Do you build on a local hosting environment or a live VPS/txAdmin? Both — on purpose. RAX Development writes and debugs scripts on a local FiveM / FXServer setup for speed, then deploys to a staging VPS with txAdmin for real-world testing, and finally to your live VPS with txAdmin when changes are approved. Building only on a laptop misses database load, streaming, and player behavior; building only on live production risks downtime during peak hours.
Quick answer: Local = fast Lua/UI iteration. Staging VPS + txAdmin = safe QA with MySQL and real artifacts. Live VPS + txAdmin = production. We use Git between all three. Get a quote
Three environments we use
| Environment |
Purpose |
Tools |
| Local | Scripting, UI, logic, quick restarts | FXServer on dev PC, local MySQL or Docker, editor + Git |
| Staging VPS | Integration test before players see it | txAdmin, same artifact line as prod, test DB |
| Live VPS | Production community | txAdmin, monitored restarts, backups, low-pop deploy windows |
Why we do not build only locally
- Your home PC rarely matches VPS CPU/RAM and player slot load
- Streaming (cars, MLOs, clothing) behaves differently under real ping and slot counts
- MySQL timing, connection pools, and peak-query issues show up on the server (peak DB guide)
- txAdmin schedules, permissions, and restart flows are production tools
- OneSync, artifacts, and game build must match what players run
Why we do not build only on live production
- Untested resources can crash the server mid-peak
- Economy or job script bugs affect real player balances
- No rollback story without Git and backups
- Staff and players see half-finished features
Staging on a separate VPS (or a hidden staging port on the same machine with isolated DB) is standard on professional launch-ready builds.
What txAdmin does in our workflow
- Start/stop/restart FXServer from a web panel
- Scheduled restarts and crash recovery
- Console access for deploy verification
- Player list and basic moderation during testing
- File manager for emergency hotfixes (Git remains source of truth)
We install and configure txAdmin on Dedicated VPS packages or on VPS credentials you provide. txAdmin is not a substitute for version control or database backups.
Typical build flow (local → staging → live)
- Kickoff — Framework (QBCore / ESX), script list, VPS access or new hosting
- Local dev — Custom Lua/UI, unit-style logic checks, Git commits
- Staging VPS —
git pull, resource ensure order, MySQL migration test, 2–5 staff testers
- Performance pass — Artifact/game build check (safe artifacts), stream audit if needed
- Live deploy — Low-population window, monitor console, enable staff logs
- Handoff — txAdmin login, README, backup schedule, optional dev standby
What you need to provide
- Option A: Root/Administrator access to your existing VPS (Windows or Linux)
- Option B: Order RAX Dedicated VPS and we provision txAdmin + FXServer
- Separate staging instance recommended for communities launching with 32+ planned slots
- Domain / Cfx.re server listing when you are ready to go public
Local setup (what “local hosting” means)
“Local” means an FXServer instance on a developer machine or a private dev box — not players connecting from the internet. We use it for:
- Custom scripts and NUI / React / Vue UIs
- ESX → QBCore porting before staging (conversion guide)
- Debugging event flows without affecting your community
You do not need to run a local server yourself unless you want to — we handle dev environments and show you txAdmin on the VPS you own.
How RAX Development helps
- Provision staging + live VPS with txAdmin and MySQL
- Match artifacts and game build to your target player client
- Deploy via Git with documented restart steps
- Server builds from $99, full custom timelines quoted
- Post-launch standby for hotfixes on staging first
US Navy Veteran, 13 years IT. Reviews · Shop · Contact
Related: txAdmin developer permissions ·
Launch timeline ·
Dedicated VPS ·
Git version control ·
Before starting a community
Conclusion
Do you build on a local hosting environment or a live VPS/txAdmin? We use both: local for fast development, staging VPS + txAdmin for safe testing, and live VPS + txAdmin for production. RAX Development provisions and documents all three so your FiveM launch is stable, not experimental.