QuantDingerQuantDingerv5.7.1 Docs Docs home
中文 GitHub
View Markdown source

QuantDinger post-installation setup

Installation alone does not make an instance safe or usable. This checklist turns a newly started stack into a maintainable research and backtesting system.

1. Administrator security

Sign in with the installer-created administrator, verify the email, replace any temporary or shared password, minimize administrator membership, and confirm system/browser time and time zone.

2. Site and deployment mode

  • Match FRONTEND_URL to the real web and H5 origins.
  • Use self_hosted for personal systems and saas only for multi-user hosting.
  • Set ENABLE_REGISTRATION=false when public registration is unnecessary.
  • Set ALLOW_LOCAL_DESKTOP_BROKERS=false when the server cannot reach desktop brokers.
  • After .env changes, run docker compose up -d to recreate affected services.

3. AI and market data

Add and test one model provider. Keep model secrets server-side. Configure the target market provider, test historical and current data, and verify instruments, venue, currency, time zone, adjustment, and freshness.

4. Notifications and identity

Configure and test required email, SMS, or Telegram channels. Production OAuth callback URLs must exactly match HTTPS origins. See email, SMS, Telegram, and OAuth.

5. Account and trading boundaries

Begin with paper or read-only accounts. Grant no withdrawal permission, verify account type, settlement currency, time zone, and order minimums, and use signal or paper mode for the first deployment.

6. Backup and monitoring

Complete a backup and restore drill before valuable data accumulates. Monitor containers, disk, database connections, queue lag, workers, and certificate expiry. Define upgrade, rollback, and log-retention procedures. Store an encrypted .env backup separately from public database backups.

7. Acceptance

Verify web and H5 login, backend health, one AI and market provider, one research task, one backtest, notification delivery, backup restore, user isolation, and disabled live trading.

Continue with the 30-minute quickstart or first run. Administrators should also read the configuration reference, backup and restore, and upgrade and rollback. If a step fails, use the error knowledge base, installation FAQ, or administrator troubleshooting.