Referencing: https://loomio.conjured.ink/d/abrCuxhp/docker-deployment-strategy
Codeberg, similarly to github and other code hosting platforms, has the capacity to host docker images. As such, I have the following proposal:
Create and upload docker images based from both Ubuntu and Alpine (or just Alpine?) on the on-release-tag.yml plan. This docker image should have a custom script as an entrypoint with the following behavior:
- If there is no
configdirectory mounted to it, print out instructions of which directories need to be mapped. We can differentiate this from a mapped directory by placing a single dummy file in it with a known md5sum - If the config directory is mapped but empty, initiate it by copying the contents of the
configdirectory from our source control repository - passing no arguments or passing any other arguments will run silverfish as normal with those arguments being passed to silverfish
Later, create a deployment script that can set everything up with user prompts
Referencing: https://loomio.conjured.ink/d/abrCuxhp/docker-deployment-strategy
Codeberg, similarly to github and other code hosting platforms, has the capacity to host docker images. As such, I have the following proposal:
Create and upload docker images based from both Ubuntu and Alpine (or just Alpine?) on the `on-release-tag.yml` plan. This docker image should have a custom script as an entrypoint with the following behavior:
* If there is no `config` directory mounted to it, print out instructions of which directories need to be mapped. We can differentiate this from a mapped directory by placing a single dummy file in it with a known md5sum
* If the config directory is mapped but empty, initiate it by copying the contents of the `config` directory from our source control repository
* passing no arguments or passing any other arguments will run silverfish as normal with those arguments being passed to silverfish
Later, create a deployment script that can set everything up with user prompts