This page answers common installation, upgrade, and post-deployment questions. See installation troubleshooting for database-password, migration, and image-pull recovery.
Docker with Compose v2 is required. Personal systems should have at least 4 cores and 8 GB RAM; concurrent AI, backtest, and trading workers benefit from 8 cores and 16 GB. Public hosts also need a domain, HTTPS, firewall, and backup capacity.
Run docker version, docker info, and docker compose version. A failed docker info means the daemon is stopped or the user lacks access. A failed docker compose means Compose v2 is missing. On Windows, verify Docker Desktop and WSL 2.
Run:
docker compose ps
docker compose logs --tail 200 backend
docker compose logs --tail 100 frontendCheck port collisions and the backend health endpoint. A visible frontend with failed login/API calls usually indicates the backend, reverse proxy, or FRONTEND_URL.
There is no universal default password. The installer creates an administrator. Use password recovery or administrator troubleshooting; never copy purported default credentials or edit password hashes directly.
PostgreSQL, Redis, and Kafka use Docker named volumes; configuration is in the installation .env. Removing containers normally keeps volumes, but docker compose down -v deletes them. Back up both database data and required configuration before moving hosts.
Rerun the installer or run docker compose pull, docker compose up -d, and docker compose ps. Pin IMAGE_TAG in production, back up first, read release notes, and verify health, migrations, workers, and critical flows afterward.
Diagnose logs and health first. Rerunning the installer safely synchronizes configuration, but deleting the directory, .env, or volumes can rotate secrets and permanently lose data.
Use docker compose stop or docker compose down, and retain the installation directory and named volumes. Use down -v only after a verified backup and an explicit decision to erase data.
Windows can host the server and build Android. iOS signing and archives require macOS, Xcode, and an Apple Developer account. See mobile client deployment.
The phone's localhost is the phone itself. Use a LAN-reachable address or HTTPS domain and check the firewall, certificate, and API URL. Production apps should not depend on plaintext HTTP.
Normally only SSH 22, HTTP 80, and HTTPS 443. Keep 5000, 5432, 6379, and 29092 on loopback or private networks.
Environment is read when a container is created. Run docker compose up -d --force-recreate <service-name> and confirm you edited the active Compose project directory.
Align the first FRONTEND_URL, provider callback, reverse-proxy protocol headers, and HTTPS origin exactly. Include both desktop and mobile origins when both are supported.
No. It also requires tenant isolation, verified email, idempotent billing webhooks, recovery, alerts, auditing, Terms, and Privacy. Follow the SaaS deployment guide.
Use installation troubleshooting, administrator troubleshooting, cloud deployment, the notification guides, or the live-trading safety checklist.