Commit deacd247 authored by John Jarvis's avatar John Jarvis

Add envs screenshot.

parent 9bf8ca0e
Pipeline #25345121 passed with stages
in 4 minutes
......@@ -45,8 +45,11 @@ deploy_draft:
script:
- make clean
- export S3_BUCKET=draft.jarv.org
- export DIST_ID=E1B0Q0MMPJQ79F
- export DISTID=E1B0Q0MMPJQ79F
- make s3_upload
environment:
name: draft
url: https://draft.jarv.org
deploy_prod:
image: registry.gitlab.com/jarv/jarv.org/ci-image
......@@ -54,8 +57,11 @@ deploy_prod:
script:
- make clean
- export S3_BUCKET=jarv.org
- export DIST_ID=EEN9NFVIDRTGS
- export DISTID=EEN9NFVIDRTGS
- make s3_upload
environment:
name: jarv
url: https://draft.jarv.org
only:
- master
```
......@@ -68,6 +74,11 @@ Some notes about the setup:
* Every time the deploy happens, an invalidate is sent to the cloudfront distribution in front of it.
* Since I am no longer using GitHub pages, the blog is hosted in an S3 bucket so the CICD pipeline does an `aws s3 sync ...` to get the static files on the bucket.
There is a special key named `environment` that hints to GitLab that the stage is a deploy step. With this the URL provided will show up under operations->deployments like this:
<img src="{attach}static/jarv-envs.png" width="600px" alt="envs"/>
That's it! It couldn't be simpler and I think one of the nicest things about this setup is the ability to use the GitLab web ide to make quick changes.
_Disclaimer: I work for GitLab though the opinions here are my own._
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment