jR4dh3y/BoxBox v0.2.0

BoxBox v0.2.0

on GitHub

BoxBox v0.2.0

This release completed the BoxBox rename work and added upgrade guardrails for older FileManager-style deployments.

Correction: the original v0.2.0 notes and image included some v1.0 wording in migration warnings/docs. The release version is v0.2.0; that wording is corrected in v0.2.1. Do not retag v0.2.0; use v0.2.1 or newer for corrected strings.

Highlights

• Renamed stale FileManager project identifiers to BoxBox across backend imports, Docker deployment files, docs, and UI text.
• Added release guardrails, GitHub templates, and Docker release workflow documentation.
• Added runtime compatibility for deprecated FM_* environment variables so older deployments can upgrade without a hard start failure.
• Added startup warnings that tell operators the exact BOXBOX_* replacement for each deprecated FM_* variable.
• Added deprecated /etc/filemanager/config.yaml fallback support with a warning to move to /etc/boxbox/config.yaml.
• Added a check-only migration helper that reports legacy env, Compose, and Docker volume names without editing files or changing Docker state.
• Updated release, Docker, configuration, and troubleshooting docs with migration and failure-handling notes.

Upgrade Notes

Old FM_* variables still work in this release, but BOXBOX_* values take precedence when both are set. Rename old variables before a future breaking release:

• FM_JWT_SECRET -> BOXBOX_JWT_SECRET
• FM_USERS_<username> -> BOXBOX_USERS_<username>
• FM_RATE_LIMIT_RPS -> BOXBOX_RATE_LIMIT_RPS
• FM_ALLOWED_ORIGINS -> BOXBOX_ALLOWED_ORIGINS
• FM_PORT -> BOXBOX_PORT
• FM_HOST -> BOXBOX_HOST
• FM_MAX_UPLOAD_MB -> BOXBOX_MAX_UPLOAD_MB
• FM_CHUNK_SIZE_MB -> BOXBOX_CHUNK_SIZE_MB

Use v0.2.1 or newer for the correctly named migration checker:

scripts/check-0.2-migration.sh

The checker is read-only. It exits 0 when no legacy settings are found, 2 when migration work is detected, and 1 for script/runtime errors.

If you migrate Docker named volumes, keep old filemanager-* volumes until the copy succeeds. Do not start with new boxbox-* volume names after a failed copy; remove/recreate the partial target or copy into a fresh target first.

Validation

• go test ./...
• go test ./internal/config
• bash -n scripts/check-1.0-migration.sh
• Docker upgrade rehearsal from ghcr.io/jr4dh3y/boxbox:v0.1.8 to the current image using isolated legacy filemanager Compose names and FM_* env vars.