- Built and tagged
3,3.19and3.19cto the last commit prior to merging the 3.20 development branch. - This should facilitate running
3.19while this project addresses3.20migration issues.
- Will now create and run as user
sbbs(1000)and groupsbbs(1000)instead of root. Passwordless sudo is setup in the environment
linux/x86-64builds only for now... ARM builds have been too problematic.- Removed 3.19b from docker images, they were broken on AMD and some Intel platforms.
- Stale Nightlies removed.
latest,3and3.19are from a recent nightly commit.nightlybuilds are working again, the latest commit does not match manually pushed dates, this should clear when there's a future nightly commit.
You now only need to mount a single directory . to /sbbs-data, if you were
using the example docker-compose, you should be able to simply switch out the
volume path(s) for a single entry. If you are overriding the web directory, you
should still mount this as mydir:/sbbs/web which will work properly inside the
container. Do not mount ./backup to /backup, this will by symlinked to
/sbbs-data/backup
/sbbs/scripts/sbbs - will appear higher in the PATH statement before
/sbbs/exec/sbbs this is intentional as it will run the initialization process
before starting, this will appropriately link the directories in question from
/sbbs-data to /sbbs inside the runtime instance.