FreeTool
fxManager
by fxManagerProject · version 2026.11.11 · updated 3 days ago
No reviews yet
- Downloads
- 0
- Reviews
- 0
- Size
- 880 KB
- Code check
- Checked
- Licence
- AGPL-3.0
- Released
- Nov 2026
fxManager is an alternative webpanel to handle fxserver to txAdmin
A self-contained, cross-platform admin panel for FiveM & RedM servers.
Single binary deployment - no runtime dependencies required on the target machine.
Each app/package will have it's own more detailled structure in it's README.
Development
The React dev server runs on
Code Quality
**Game Resource ( [
Commands specific to the game-side resource and NUI:
Migrations are automated via a synchronization utility. Do not manually edit the migration registry.
Adding a Migration
Biome handles linting and formatting (replacing ESLint and Prettier) using a single, high-performance configuration at the root.
Releasing
Releases are driven by a maintainer - the workflow never commits, pushes, or tags. To cut a new release:
Building
Turbo caches build outputs - subsequent builds only rebuild what changed.
Output in
The panel will be available at
2. Install the resource
Variable, Default, Description
Errrh anything else ?
Single binary deployment - no runtime dependencies required on the target machine.
WARNINGStructure
This project is still in intensive development, it is not to be considered stable until av1.0.0+release.
If this repository is public, it's for transparency, feedback and open source contributions to help it achieve this milestone.
Each app/package will have it's own more detailled structure in it's README.
fxManager/
├── apps/
│ ├── core/ # Process Manager & Webserver
│ ├── resource/ # FxServer resource to connect to panel
│ └── webpanel/ # React SPA served by the webserver
├── packages/
│ ├── database/ # Drizzle schema & Migration handler
│ ├── shared/ # Enums, types, and utils
│ └── ui/ # Shared React ShadCN components
├── biome.json # Root linting/formatting
├── package.json # Workspace definitions
└── turbo.json # Build pipeline configDevelopment
**Install dependencies**
bun install
**Start system**
bun devThe React dev server runs on
:5173 and proxies API/WS calls on :3000.Code Quality
bun check # lint + format + fix (recommended during dev)
bun lint # lint only
bun format # format only
bun typecheck # tsc --noEmit across all packages (via Turbo)
bun db:studio # open Drizzle Studio to browse the database (optional)
bun db:migrate # creates a new migration file**Game Resource ( [
apps/resource](https://github.com/fxManagerProject/fxManager/blob/main/apps/resource) )**Commands specific to the game-side resource and NUI:
- **
bun web:dev** – Runs the Vite dev server for the NUI frontend. - **
bun watch** – Rebuilds the resource automatically as you save files. - **
bun deploy** – Bundles the resource and copies it to the path defined in yourDEPLOY_PATHenvironment variable.
Migrations are automated via a synchronization utility. Do not manually edit the migration registry.
Adding a Migration
- Generate Migration: Run the generation script using:
bun run db:migrate
- Describe: When prompted, provide a short description of the changes.
- Sanitize and split the SQL queries.
- Create a structured
.tsmigration file inpackages/database/src/migrations/migrations/. - Register the new migration in
packages/database/src/migrations/index.ts.
- Immutability: Never modify a migration file (
.sql,.ts, or.json) once it has been deployed to production. - Automation: Migrations are applied automatically on the next application startup.
Biome handles linting and formatting (replacing ESLint and Prettier) using a single, high-performance configuration at the root.
Releasing
Releases are driven by a maintainer - the workflow never commits, pushes, or tags. To cut a new release:
bun ./scripts/release.ts v0.3.3Building
**Build for both platforms**
bun run build
**Build for a specific platform**
bun run build --target=linux
bun run build --target=windowsTurbo caches build outputs - subsequent builds only rebuild what changed.
Output in
dist/:
dist/
fxmanager-linux ← Linux binary
fxmanager-windows.exe ← Windows binary
assets/ ← UI assets - must stay next to the binary
resource/ ← Drop into your server's resources/ folder
IMPORTANTDeployment1. Run the binary
Theassets/folder must remain in the same directory as the binary when deploying. The server resolves it relative to its own location at runtime.
your-deploy-folder/
fxmanager-linux (or fxmanager-windows.exe)
assets/
.env
./fxmanager-linux # or fxmanager-windows.exeThe panel will be available at
http://your-server-ip:4000.2. Install the resource
- Copy
dist/resource/into your server'sresources/folder asfxManager - IMPORTANT Do not add
ensure fxManagerto yourserver.cfgor attempt to stop it
Variable, Default, Description
FXSERVER_EXECUTABLE, ./FXServer, Path to FXServer binaryFXSERVER_DATA_PATH, ./server-data, Path to server-data folderFXSERVER_CFG, server.cfg, Config file name inside data pathPANEL_PORT, 3000 (opt), Web panel portCOOKIE_SECRET, N/A (opt), Defines the secret for cookie signDEPLOY_PATH, N/A, Used in development for the resourceErrrh anything else ?