Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
go
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
21
Issues
21
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
SRCT
go
Commits
d6f2bc64
Verified
Commit
d6f2bc64
authored
Feb 10, 2018
by
David Haynes
🙆
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs changes
- a constant state of disaster
parent
86aed9b7
Pipeline
#2108
passed with stages
in 2 minutes and 32 seconds
Changes
3
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
23 additions
and
14 deletions
+23
-14
CONTRIBUTING.md
CONTRIBUTING.md
+11
-7
README.md
README.md
+12
-0
go-cleanlinks.cron
go-cleanlinks.cron
+0
-7
No files found.
CONTRIBUTING.md
View file @
d6f2bc64
...
...
@@ -18,13 +18,15 @@ the issues page.
If you decide to take on an issue for Go you will need to work in a branch off
of the current development branch (ie.
`2.3-dev`
with 2.3 being the version in
development).
development).
This can be done with the following chain of
`git`
commands within
`go/`
:
git pull
git checkout 2.3-dev
git checkout -B ##-shortdescription
```
sh
git pull
git checkout 2.3-dev
git checkout
-B
##-shortdescription
```
**Note:**
...
...
@@ -34,9 +36,11 @@ does.
**Example:**
git pull
git checkout 2.3-dev
git checkout -B 102-readmeUpdates
```
sh
git pull
git checkout 2.3-dev
git checkout
-B
102-readmeUpdates
```
If you are working on something that does not have an issue please open a new
issue before creating your branch.
...
...
README.md
View file @
d6f2bc64
...
...
@@ -221,6 +221,18 @@ repository and is named go-cleanlinks.cron. Drop this in cron.hourly and
change the paths so that they point to the virtualenv activate script and
manage.py.
## Production cron job
```
sh
#!/bin/bash
# Cron job to automatically expire outdated links, put this in cron.hourly
ACTIVATE_PATH
=
/path/to/virtualenv/activate
MANAGE_PATH
=
/path/to/go/manage.py
source
${
ACTIVATE_PATH
}
python
${
MANAGE_PATH
}
expirelinks
```
---
**Note:**
...
...
go-cleanlinks.cron
deleted
100644 → 0
View file @
86aed9b7
#!/bin/bash
# Cron job to automatically expire outdated links, put this in cron.hourly
ACTIVATE_PATH
=
/path/to/virtualenv/activate
MANAGE_PATH
=
/path/to/go/manage.py
source
${
ACTIVATE_PATH
}
python
${
MANAGE_PATH
}
expirelinks
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment