Repository navigation
v0.6.1 - multi-instance-on-one-host fixes
Pre-release
Pre-release
Found by deliberately installing this project from scratch, README-only, as if a brand new user
-- on a host that already runs another checkout of this app.
Fixed
git clone ... && cd redroid-forgecollided if a checkout already existed at that default
path -- README now shows cloning into a differently-named directory instead.container_namewas hardcoded toredroid-forgewith no override, so even a second checkout
in its own directory still collided on the container name. Now reads
${CONTAINER_NAME:-redroid-forge}-- same default as before, no change for a single-instance
host.- A failed
app.listen()(e.g. the defaultPORT=8080already taken by something else on the
host) was silently swallowed by the genericuncaughtExceptionhandler meant to survive a bug
in a single request, not a startup failure -- the container stayed "Up" with the Express server
never actually listening, no real signal anything was wrong. A failed bind is now fatal, so
restart: unless-stoppedshows it honestly as a crash-looping container instead.
Added
.env.example-- every env var was only discoverable by readingdocker-compose.yml's own
comments before this. DocumentsPORT/CONTAINER_NAMEup front plus the rest.
See CHANGELOG.md
for the full detail.