I've kept the codex-container.sh version going for this eventuality.
Those scripts are for running the docker command with all the ENV vars and settings. Whatever does that does NOT have to be Powershell if you don't want it to be.
Poweshell is awesome because no external tools are needed to modify dates, or do math, or generate JSON or XML, both of which are first-class citizens. Also, in powershell things are objects not strings, so passing something along with a | is much more powerful. Still, if someone doesn't like something, there's always bash!
I represent one of those stars. N8N is an amazing system. I use it daily and have seen incredible progress made consistently over the past few years. Currently my team use it for processing millions of workflows each year on a very small server and it hasn't cost us a cent so I would give them more than 1 star if I could. I wouldn't build a new system without it to be honest.
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.
Here is my main use case. I have lightweight services that I need to update and deploy regularly (until I movee to K8s or a proper production env). Using pooshit, I can push my entire local dev folder to a remote server then destroy the old image, rebuild the new image and spin up a new container with one call. Your config file contains your remote config. You need nothing in between you and your remote server and it only relies on SSH and docker, nothing else, no middleman, repos, and no deployment containers running on your VM.
