Skip to Content
txAdminDeployer
Open in ChatGPTOpen in Claude

txAdmin Deployer: What it actually does

txAdmin includes a recipe-based Server Deployer for setting up a server or profile. It can download files from GitHub, install resources, import SQL and generate configuration according to the selected recipe.

It is not a built-in continuous Git deployment service. Pushing a commit to a Git branch does not automatically make txAdmin pull the branch, run pre/post-deployment hooks or expose a one-click deployment-history rollback screen. Those features require separately configured tools, if available.

Use the built-in Recipe Deployer

  1. Start FXServer in txAdmin monitor mode (without +exec server.cfg).
  2. Create a new profile or prepare a clean, backed-up deployment path.
  3. Choose Popular Recipes or a supported custom recipe.
  4. Review where the recipe downloads files, creates directories and imports data.
  5. Supply a Cfx.re server registration key  and any recipe-specific database credentials.
  6. Execute the recipe, read failures and finish with Save & Run Server.
  7. Test game joins, scripts and persistence.

See txAdmin Recipes and the upstream recipe format .

How to deploy regular code changes

For updated resources, use a controlled external Git/CI workflow or your hosting provider’s deployment feature:

  1. Commit your resource and configuration code; keep passwords/keys out of Git.
  2. Test it on a staging server against the same artifact and framework versions.
  3. Back up the active data/configuration and take a database snapshot if the release includes migrations.
  4. Transfer a known release revision to production via Git, a build artifact or a deployment service.
  5. Use txAdmin to stop/restart affected resources and read the Live Console.
  6. Verify player joins, game behavior and persistence. Keep the previous release available to roll back.

The installed txAdmin panel may offer resource controls and configuration editing, but do not confuse those controls with a Git webhook service.

Rollback

Stop the affected resource/server, restore the previous tested release and any compatible schema/data changes, and restart under supervision. A Git checkout alone cannot reverse a destructive database migration. Re-running an initial-install recipe over production can overwrite custom files.

Useful next steps: Server Backups, txAdmin Monitoring, Recipe Deployment.

BackupsMonitoring