|
|
|
@ -2,8 +2,8 @@ stages: |
|
|
|
- deploy |
|
|
|
|
|
|
|
# Deployment is done in a reverse manner. |
|
|
|
# Instead of rsyncing the files on the servers, we notify them. |
|
|
|
# They will `git pull` the master by themselves. |
|
|
|
# Instead of rsyncing (uploading) the files on the servers, we notify them. |
|
|
|
# The server(s) will `git pull` the master by themselves. |
|
|
|
deploy: |
|
|
|
stage: deploy |
|
|
|
image: appropriate/curl:latest |
|
|
|
@ -14,4 +14,4 @@ deploy: |
|
|
|
|
|
|
|
# Ideally we should test all the pages of the website |
|
|
|
# and assert that they respond with either a 2XX or 3XX HTTP status code. |
|
|
|
# That should allow us to catch badly formed Markdown, YAML or file paths.. |
|
|
|
# That should allow us to catch badly formed Markdown, YAML or file paths.. |
