Home

ITFlow MSP Edition — Deployment Wiki

How to get a running instance, back it up, and restore it. Two supported paths depending on what you're doing:

• Docker Compose — fastest way to try it, or a lightweight self-hosted deployment. Not hardened; put a real reverse proxy in front of it for anything beyond local evaluation.
• Bare Metal Install — deploy/install.sh, the recommended path for a production instance: provisions nginx, PHP, MariaDB, and Redis; sets up TLS; applies security hardening; runs the app's first-run setup.

Once you have an instance running:

• Backup and Restore — encrypted, scheduled backups (deploy/backup.sh) and how to restore one onto a fresh box (deploy/restore.sh), including disaster recovery from scratch.
• Updating and Hardening — deploy/update.sh for pulling application updates, and deploy/harden.sh for the fuller hardening pass beyond what a fresh install applies inline.

All of the scripts referenced here live under deploy/ in the main repo — this wiki explains what they do and why; the scripts themselves (and their --help output) are the source of truth for exact flags.