Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
3f8736cf
Commit
3f8736cf
authored
Aug 20, 2019
by
GitLab Bot
Browse files
Options
Browse Files
Download
Plain Diff
Automatic merge of gitlab-org/gitlab-ce master
parents
58f138de
e046a177
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
46 additions
and
0 deletions
+46
-0
doc/topics/autodevops/index.md
doc/topics/autodevops/index.md
+46
-0
No files found.
doc/topics/autodevops/index.md
View file @
3f8736cf
...
...
@@ -584,6 +584,52 @@ Unless you have a `Dockerfile` in your repo, your image is built with
Herokuish, and you must prefix commands run in these images with
`/bin/herokuish
procfile exec`
to replicate the environment where your application will run.
#### Workers
Some web applications need to run extra deployments for "worker processes". For
example it is common in a Rails application to have a separate worker process
to run background tasks like sending emails.
The
[
default Helm chart
](
https://gitlab.com/gitlab-org/charts/auto-deploy-app
)
used in Auto Deploy
[
has support for running worker
processes
](
https://gitlab.com/gitlab-org/charts/auto-deploy-app/merge_requests/9
)
.
In order to run a worker you'll need to ensure that it is able to respond to
the standard health checks which expect a successful HTTP response on port
`5000`
. For sidekiq you could make use of the
[
sidekiq_alive gem
](
https://rubygems.org/gems/sidekiq_alive
)
to do this.
In order to work with sidekiq you'll also need to ensure your deployments have
access to a redis instance. Auto DevOps won't deploy this for you so you'll
need to manage this separately and then set a CI variable
`K8S_SECRET_REDIS_URL`
which the URL of this instance to ensure it's passed
into your deployments.
Once you have configured your worker to respond to health checks you you will
need to configure a CI variable
`HELM_UPGRADE_EXTRA_ARGS`
with the value
`--values helm-values.yaml`
. Then you can, for example, run a
[
sidekiq
](
https://github.com/mperham/sidekiq
)
worker for your rails application
by adding a file named
`helm-values.yaml`
to your repo with the following
content:
```
yml
workers
:
sidekiq
:
replicaCount
:
1
command
:
-
/bin/herokuish
-
procfile
-
exec
-
sidekiq
preStopCommand
:
-
/bin/herokuish
-
procfile
-
exec
-
sidekiqctl
-
quiet
terminationGracePeriodSeconds
:
60
```
### Auto Monitoring
See the
[
requirements
](
#requirements
)
for Auto Monitoring to enable this stage.
...
...
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