You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be better if we built the container to the GHCR instead of building it on the machine itself.
Means we don't have to clone the entire repo, and instead just pull the container image from the GHCR.
There are 3 ways that I'm thinking of that we could use to automate deployment after a container build:
Webhook to something like Jenkins that pulls down the image and deploys it
A GH Action that runs after the container is built to SSH in and recomposes up
A container like Watchtower (or alternative) which constantly looks for new images for any Container running [image]:latest.
@cs-soc-tudublin/system-administrators We should chat about this this week
Add CI/CD step where container is test build first (dry run?) before deployment.
If it fails, it should not even SSH.
This will increase deployment times, but only by a few minutes at maximum. Container build time is ~1 minute.
The text was updated successfully, but these errors were encountered: