Artur Hefczyc opened 3 weeks ago
-
The error is entirely expected — the run-all.sh script depended on a pre-created PostgreSQL database named sztabdb, but I removed that script after moving to the new unified sztab Docker/Compose setup which weaves in PostgreSQL + sztab-backend + sztab-UI containers into a single working system. The new Compose files that replaced it auto-create the database correctly, but run-all.sh does not.
In short: • run-all.sh is now obsolete and no longer maintained • It still points to the old environment, which expected sztabdb to exist • The current recommended workflow is the unified sztab/ compose setup (docker-compose up --build), which works end-to-end
I will remove the script run-all.sh and instead put in place a new executable that will bring up the new env.
-
rk@tigase.net changed state to 'In Progress' 3 weeks ago
Previous Value Current Value Open
In Progress
-
Thank you for explanation. However, I still cannot find a way to run the whole thing.
I am trying to follow the README instructions instead.
Here are some examples:
sztab git:(wolnosc) cd deploy/docker docker compose up --build Compose can now delegate builds to bake for better performance. To do so, set COMPOSE_BAKE=true. [+] Building 0.0s (1/1) FINISHED docker:desktop-linux => [sztab-backend internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2B 0.0s failed to solve: failed to read dockerfile: open Dockerfile: no such file or directoryRunning:
docker compose -f docker-compose.yml up --buildResults with the same error that
sztabdbdoes not exist.I am not sure where is the problem, maybe the documentation is not up to date.
-
Artur,
I’ve been dealing with an unexpected TypeScript/UI issue over the last two days, which has delayed the release. The backend and deployment pieces are ready, but the UI needs to compile cleanly before I can ship a usable build.
The concern about run-all.sh is resolved — that script is obsolete. The replacement is the new sztab orchestrator, which handles starting, stopping, cleanup, logs, and launching the frontend, so the “missing sztabdb” issue will not occur once the updated release is pushed.
I’m working on stabilizing the UI now and will deliver the release today. I’ll keep you posted as soon as it’s ready.
Regards, Rk
-
Resolution Summary
This issue referred to problems running the legacy
run-all.shscript from Sztab 1.4, where the backend failed at startup due to a missing database (sztabdb). The script attempted to orchestrate backend, frontend, and PostgreSQL containers, but it was fragile, unmaintained, and not aligned with the evolving system architecture.As of Sztab 1.6, the entire orchestration mechanism has been replaced with the new
sztaborchestrator script (introduced in 1.5 and stabilized in 1.6). This script supersedesrun-all.shcompletely.Key Points
run-all.shis deprecated and no longer supported.- The new
sztabcommand provides:- Consistent environment setup
- Automatic database initialization
- Unified commands for
up,down,logs,build, etc. - Stable backend + UI startup
- ENV-based override options
- All instructions now reference
./sztab up, notrun-all.sh. - The failure described in this issue is not relevant to current releases because:
- The database bootstrap is now handled automatically
- Docker Compose configuration has been updated
- Backend and UI container definitions have been refactored
- Session-auth mode, DB schema init, and network bindings are all encapsulated by the new orchestrator
Action Taken
- Verified that Sztab 1.6 starts correctly via:
% ./sztab up- Verified DB initialization, backend startup, and UI availability.
- Confirmed that no part of the current system references
run-all.sh.
Final Status
Issue closed as obsolete.
run-all.shhas been fully replaced by the newsztaborchestrator in Sztab 1.6.
No further action required. -
Previous Value Current Value In Progress
Closed
| Type |
Bug
|
| Priority |
Blocker
|
| Assignee | |
| Version |
none
|
| Sprints |
n/a
|
| Customer |
n/a
|
This is in reference to @rk email from 11/11/2025 with the subject "Sztab 1.4 with basic Dashboard".
I tried to run it according to instructions, basically running the command:
By the way such a command is a great way to allow anybody for a quick test deployment.
However, I am getting error/exception from the stab-backend about missing database:
sztabdb. Here is stack trace with the exact error message: