Skip to content

BaseHarbor v0.4.24

Create and run apps locally or remotely, with leaner shared services and safer recovery.

Highlights

  • Simpler application workflows. Start with baha new, select your Core or Target with baha use, and manage the app directly from its repository. Repository-aware commands and guided Core setup get projects running with fewer steps.
  • Reliable local and remote Targets. Rootless Docker is the default. Docker and Podman operations stay on the selected Target; CLI and MCP never silently switch engines or fall back from a remote Core to a local one. The Node Connector provides authenticated remote access, including application lifecycle, logs and terminal sessions.
  • Lean shared infrastructure. Omitted HA or ha: false selects standard topology without unnecessary HA replicas. Shared Keycloak and application SQL reuse Core PostgreSQL with separate databases and users; shared Valkey isolates applications with ACL users and key namespaces. Fewer duplicate servers mean less infrastructure to run.
  • Safer upgrades and recovery. Supported PostgreSQL, OpenBao and Keycloak updates check compatible pinned images, ownership and verified backups before changing services. PostgreSQL backup/WAL recovery and authenticated etcd recovery provide controlled recovery paths for shared HA installations on Docker and Podman. Failed changes and uncertain SQL commits receive explicit reconciliation guidance.
  • Better daily developer experience. The Web Console brings Core setup, application lifecycle, logs and terminal access together behind OIDC and Core-enforced roles. Live readiness, actionable diagnostics and consented port fallback make problems easier to resolve. Cleanup protects foreign resources and retained data.

Compatibility notes

  • Use baha app sql and baha app cache, replacing the older app psql and app valkey names.
  • Existing installations retain their topology and data; no automatic migration is performed. PostgreSQL major upgrades, application-scoped PostgreSQL HA and cross-host failover remain unsupported. SQL transactions with unknown commit outcomes are not automatically replayed.