This project is designed to be operated through bin/, not through ad hoc commands.
The main idea is simple:
bin/is the control planedocs/is the knowledge basedocker/is the runtime internals
Use:
./bin/up.shThis is the normal startup path because it does more than a plain compose bring-up.
It:
- loads and patches safe runtime values into
.env - prepares host paths
- validates compose
- bootstraps the helper bind mount when required
- starts MariaDB first
- waits for DB health
- starts app services only after DB readiness
Plain bring-up commands are easy to remember, but they do not by themselves encode your project’s operational discipline.
bin/up.sh does.
That makes startup:
- more repeatable
- more observable
- less dependent on memory
- less fragile after long gaps between sessions
Use the repository in this order:
./bin/up.sh- browser installer / finalizer flow
- docs-guided recovery tools when needed
- explicit reset or recovery scripts only when you mean it