Skip to content

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 01 Aug 15:50
· 354 commits to main since this release
dd53d63

Staaash v1.0.0

Staaash v1.0.0 is the first stable release of the private, self-hosted file drive for storage you control. Please expect bugs in the early stages of v1 and do not forget to report!

Highlights

  • Browser-based file and folder management with uploads, previews, downloads, rename, move, favorites, search, trash, restore, and permanent deletion.
  • Resumable uploads, per-user storage quotas, generated ZIP downloads, and worker-managed media previews.
  • Public file and folder sharing with optional passwords, expiry dates, download controls, media previews, revocation, and canonical public URLs.
  • Multiple-user administration with temporary passwords, required password changes, session controls, and per-user storage limits.
  • Operator-facing health, integrity, storage, job, update, and reconciliation views.
  • Crash-recoverable storage mutations backed by a durable PostgreSQL journal, leases, fencing, atomic same-volume filesystem operations, and fail-closed ambiguity handling.

Deployment requirements

  • Docker Engine or Docker Desktop with the Docker Compose plugin.
  • Linux AMD64. A native ARM64 image is not published for v1.0.0.
  • PostgreSQL 18, supplied by the release Compose stack.
  • Local, same-volume app-managed storage with atomic rename and working file and directory fsync. Network filesystems, object-storage mounts, and S3-compatible backends are not supported storage locations.

Staaash is a file drive, not a backup system. Keep an independent backup of important data and test restores regularly.

Installation

Download docker-compose.yml and example.env from the assets attached to this release, rename example.env to .env, set a secure DB_PASSWORD, then start the stack with:

docker compose up -d

Open http://localhost:2113 and complete initial setup. The first account becomes the owner.

Upgrade notes

Compatible PostgreSQL 18 RC/v1 installations can upgrade in place after taking a complete offline backup. Alpha and beta deployments are unsupported development history and require a fresh installation; do not reuse their internal database or storage directories as current data directories.

Release hardening

This stable release includes the final storage-mutation recovery work, release-workflow integrity and recovery hardening, security dependency fixes, and the complete pre-release production revalidation and backup/restore drill.

Full Changelog: v1.0.0-rc.7...v1.0.0