CasaOS deployment support is now working with a dedicated app store branch #31

PaulAtkins88 · 2026-04-09T02:43:15Z

PaulAtkins88
Apr 9, 2026
Maintainer

I’ve finished a full CasaOS deployment pass for Bucketwise Planner and wanted to share the outcome.

Added Docker image publishing for tagged releases using Docker Hub
Published release images for:
- slsadmin/bucketwise-planner-backend:0.4.7
- slsadmin/bucketwise-planner-frontend:0.4.7
Added a safe backend schema mode for managed environments:
- DB_SCHEMA_MODE=manual prevents routine restarts from automatically applying schema changes
Kept the public self-hosted Docker Compose path intact for existing users
Created and cleaned a dedicated casaos-appstore branch that contains only CasaOS app-store source files
Validated a successful CasaOS install against an existing external PostgreSQL database

Use the custom app store ZIP source from the casaos-appstore branch
Leave the Network field blank during install
Leave container names blank
Set the Web UI port to 5555
Keep DB_SCHEMA_MODE=manual for normal operation
The CasaOS package is designed to connect to an existing PostgreSQL instance rather than provisioning its own database

The frontend proxies API traffic internally to the backend service over the Compose network
That means the service wiring matters, but explicit Docker container names do not need to be set

Main branch docs now include the validated CasaOS install settings
The casaos-appstore branch README documents the working install path
The CasaOS app-store source is now unambiguous and no longer includes unrelated root repo files

CasaOS deployment path is working
Docker release workflow is in place
Public deployment path remains supported
The remaining manual operational step is rotating any secrets that were exposed during setup and debugging

If anyone else is testing Bucketwise on CasaOS and wants the exact source URL or install values, I can post the exact working configuration.