[⚙️🐳] Added image build action #40
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds a new GitHub Action which will build the image to the GitHub Container Registry.
This closes #24
This will allow a new CI/CD approach that will make it easier to deploy.
Some suggested deployment approaches:
1. SSH GitHub Action
Modify the current deployment action to run after the image is built.
The current action requires the entire source code to be cloned onto the server, and then built and deployed locally. This isn't the most efficient approach time-wise or resource-wise, as cloning and then building takes time, and it requires physical storage space.
Also, if the build & deployment stage fails at any point during the SSH phase, it is still marked as a successful run. Which is problematic.
2. Watchtower Container
A Watchtower Container (Or similar system) occasionally polls the remote image repository to see if there is a new version of the container image. If so, it pulls it down and starts the new image.
This means only the current image is stored, minimising storage requirements, and additional actions are not required, as all the checks and work is handled server-site.