[scottydelta]

I understand what you are trying to do but you should checkout dokploy or coolify.

You push to github, github action builds it and hits dokploy webhook and it pulls your github code and build and deploy on that server.

This is more reliable and industry way. What you are doing requires same amount of time to deploy and requires manual intervention every time.

For once i thought you were moving code to server and then you just restarted container and it worked without having to build. I have done it in the past due to some unique requirements where dependencies are in docker image and code is copied from local to server and docker image took code from server on start.

[marktolson]

Not sure if you read the description but I clearly stated that I wanted no middleman, so I'm not sure how this solves my use case. Also not sure how it requires the same amount of time, and 'manual intervention every time'? You provision a remote server, install docker then update the local config file and it's done. One line deployments everytime. And why would I update the code inside the container when you need a build process to install dependencies? If you want to update code while the app is running then restart, then docker is not the right solution.

Additionally there are a million different and better ways to deploy services, this suits the use case I described.

[coded_monkey]

There is nothing “industry way” about letting CI automatically deploy your production environment.

[scottydelta]

CI/CD are used for deploying to all kind of environments. For production, the triggers are different. Instead of deploy on PR merge, you would define the trigger as tag creation. Now when you make a release mauanlly on github, it will create a tag which in turn would trigger deployment.