Changes

Page history
clarify what the SITE_URL is for (ci-templates#1) authored by anarcat's avatar anarcat 
... and it's not for nothing! :)
Hide whitespace changes
Inline Side-by-side
service/static-shim.md
View page @ a76a4043
...@@ -427,6 +427,12 @@ to only a *specific* site update, with a wrapper that will call ...@@ -427,6 +427,12 @@ to only a *specific* site update, with a wrapper that will call
`rsync` but limited to a specific directory. We also allow connections `rsync` but limited to a specific directory. We also allow connections
only from GitLab over SSH. only from GitLab over SSH.
This implies that the `SITE_URL` provided by the GitLab CI job over
SSH, whether it is for the `rsync` or `static-update-component`
commands, is actually ignored by the backend. It is used in the job
definition solely to avoid doing two deploys in parallel to the same
site, through the GitLab [`resource_group`](https://docs.gitlab.com/ee/ci/resource_groups/) mechanism.
The public part of that key should be set in the GitLab project, as a The public part of that key should be set in the GitLab project, as a
File variable called `STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY`. This way File variable called `STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY`. This way
the GitLab runners get access to the private key and can deploy those the GitLab runners get access to the private key and can deploy those
... ...
......