Helper used DATA_DIR (in-container path) for bind-mount source.
Daemon created phantom /data on host, log + staging went there
instead of /opt/amnezia-admin-data. Resolve HOST_DATA_DIR via env
or docker inspect; place staging under DATA_DIR so single mount
exposes both log and install.sh to helper.
Co-authored-by: Cursor <cursoragent@cursor.com>
One env enables community + ALLOW_COMMUNITY_* and writes marker in DATA volume
for idempotent reinstalls without re-export.
Co-authored-by: Cursor <cursoragent@cursor.com>
pipefail aborted the script after download when inspect succeeded but port
mapping was unavailable (Stopped/Created).
Co-authored-by: Cursor <cursoragent@cursor.com>
Poll community-install-last.log after «Установить PRO» with GET
/api/community/install-log; preserve log DOM across banner redraws.
Co-authored-by: Cursor <cursoragent@cursor.com>
Run install.sh in a disposable docker:26-cli container after docker rm
FREE/landing/stale PRO; keeps working after API response. Legacy in-panel
bash retained when COMMUNITY_DISABLE_DOCKER_CLI_HELPER=1. Persist related
env vars in install.sh from previous container.
Co-authored-by: Cursor <cursoragent@cursor.com>
- Restore ALLOW_COMMUNITY_GITHUB_ACTIVATION and related vars from old amnezia-admin
- Pick free LANDING_PORT when host :80 is busy
- README: FAQ token field, 8080 vs PRO, landing port
Co-authored-by: Cursor <cursoragent@cursor.com>
Ship full install stack with .amnezia-panel-edition=community; docs and
footer point to Boosty/PRO. Managing peers, export, cascade and WARP
require private PRO build.
Co-authored-by: Cursor <cursoragent@cursor.com>
