Skip to content

Production launch checklist ​

Use this checklist for your installation. A clean compile and a successful HTTP response do not prove that a community’s world, permissions, email and game-client flows work.

Build and configuration ​

  • [ ] Build from the intended source revision with the pinned compiler/dependencies.
  • [ ] Configure your own name, domain, ports and credentials.
  • [ ] Confirm all required components/plugins load on the actual host OS.
  • [ ] Verify MySQL and ColAndreas startup success in log.txt.
  • [ ] Ensure only one game process owns the directory/port.
  • [ ] Leave unused Discord, voice and custom model features off.

World and gameplay ​

  • [ ] Replace map TODO positions, including public spawn, DMV, medical locations and admin jail.
  • [ ] Create and test entrances/exits, interiors and virtual worlds.
  • [ ] Configure starter factions, leaders, uniforms, lockers and equipment.
  • [ ] Create intended vehicles, dealerships, shops, businesses and job service points.
  • [ ] Complete a crate delivery, including partial loading, unloading, payment and cancellation.
  • [ ] Test vehicle respawn/storage behaviour and injury/recovery using ordinary characters.

Web and account security ​

  • [ ] Complete registration, verification, quiz, character creation and game login.
  • [ ] Verify mail delivery from your own sender to an external inbox.
  • [ ] Complete password recovery and confirm used links cannot be replayed.
  • [ ] Enable/test web 2FA on a test account before relying on it for staff.
  • [ ] Check permanent and temporary bans, session revocation and staff demotion.
  • [ ] Test lower staff ranks and ordinary faction members, not only Developer.
  • [ ] Serve the public app over HTTPS with the correct origin/proxy settings.

Operations ​

  • [ ] Test ACP start/stop with the agent-owned process.
  • [ ] Check console/stream restrictions, logs and audit-write failures.
  • [ ] Persist the database, models and relevant runtime data across redeployment.
  • [ ] Keep agent/database access private and restrict backend access.
  • [ ] Restore a backup into a separate test installation.
  • [ ] Document a recovery contact and maintenance process for your community.

Distributing your fork ​

Export intended source and example configuration rather than zipping your working directory. Exclude real .env files, configured credentials, dumps, logs, preview accounts, uploaded assets you cannot redistribute and generated collision data. Preserve licences and contributor notices.

The framework project website/documentation is maintained separately from the downloadable framework. Your community website template remains in web-platform/web/.

Verification limits ​

The source has been checked with Windows compilation, web/agent tests, a clean MariaDB import and local account/agent flows. Full GTA-client playtesting and Linux/EasyPanel deployment need testing on the host you actually use. The guides identify optional/placeholder features instead of treating them as complete production services.

Open-source roleplay foundations for open.mp. Bring your own world.