Dockermon Container Remote Github Updates
When you create a Dockermon container you can enable Github updates and even select a specific branch to launch the backend and frontend from. By using environment variable in the dockermon container, the startup scripts will update the container’s app code and startup scripts with the files contained in Dockermon App Repo
To Enable Github Updates
(default in the docker-compose.yml):
DOCKERMON_ENABLE_GIT_UPDATE=1
DOCKERMON_ENABLE_GIT_BRANCH="main"
Github Updates Branch Selection
DOCKERMON_ENABLE_GIT_UPDATE=1
DOCKERMON_ENABLE_GIT_BRANCH="some_branch"
What’s happening here?
The process allows the automatic updates to the latest code. The code in the repos above is production builds of the Nest backend and Next.js frontend.
The dockermon container script in /app/dockermon-app/start.sh specifically does this:
#/bin/sh
if [ $DOCKERMON_ENABLE_GIT_UPDATE ]
then
cd /app
if [ ! -d "/app/dockermon-app/.git" ]
then
git clone https://github.com/drumfreak/dockermon-app.git
fi
cd dockermon-app
if [ $DOCKERMON_ENABLE_GIT_BRANCH ]
then
git checkout $DOCKERMON_ENABLE_GIT_BRANCH
fi
git pull
fi
cd /app
/app/dockermon-app/app-start.sh
... resume normal launch
If you are concerned about security of remote updates, you may update your docker-compose.yml
and modifiy ENV section as follows:
To Disable github Updates:
DOCKERMON_ENABLE_GIT_UPDATE=0
Beware that there are no notices that updates have occured yet. You may one day boot up and see a whole new interface. Surprise!! At least it’s free.
Read More:
- Dockermon Main
- Dockermon Features
- Dockermon Inspiration
- Dockermon Backend Details
- Dockermon Frontend Details
- Dockermon socat Socket Pipe
- Dockermon Container Image Build
- Dockermon Container Init Process
- Dockermon Container Github Updates
- Dockermon Remote Host Management
- Dockermon Host Launcher - Mac OS
- Dockermon FAQ