Skip to content
BoltiseBoltiseBoltise

Your First Project

A project in Boltise points at a server-data folder and tracks its framework, resources, database connection, and FXServer artifacts. You either create a fresh one or import a server you already run.

This page is the quick path. For a reference of every wizard option, see the Project Wizard.

Import an existing server

Section titled “Import an existing server”

Use a development copy for your first resource installation. Check that the copied configuration connects to a separate test database before importing it.

The fastest start. In the wizard, choose Create New Project, then pick Import Existing at the template step.

  1. Basics: name the project and choose the game (FiveM or RedM).
  2. Template: select Import Existing and point Boltise at your current server folder.
  3. Database: connect to MySQL, then create or import SQL as needed.
  4. Artifacts: reuse the detected FXServer path, or set or download one.
  5. Open project.

On import, Boltise detects:

  • Framework: QBCore, ESX, QBox, VORP, or custom.
  • Resources: every enabled resource in server.cfg.
  • Database: the MySQL connection from your config.

Import registers and configures your existing folder in place. It does not overwrite your structure.

Create a new server

Section titled “Create a new server”

Starting fresh:

  1. Click Create New Project.
  2. Basics: set the name, location, an optional icon, and the game.
  3. Template: choose Framework or Standalone.
  4. Configure server settings, keys, and the database.
  5. Review and create the project.
  6. Deploy the template recipe, if one exists for the selected framework.
  7. Set up FXServer artifacts (download or browse to an existing build).
  8. Open project.

Project structure

Section titled “Project structure”

For new Framework or Standalone projects, Boltise generates a layout like this:

server-data/
├── resources/
│   ├── [core]/        # framework and its dependencies
│   ├── [standalone]/  # resources that need no framework
│   └── [assets]/      # maps, vehicles, clothing
├── server.cfg         # server configuration
└── myLogo.png         # optional, if you picked an icon

The bracketed folders are a FiveM convention, not a Boltise one: FXServer treats any [name] folder as a group and loads the resources inside it. Deploying from a recipe skips this scaffold — the recipe lays out its own resources/.

Teaching the AI about your server

Section titled “Teaching the AI about your server”

Create a file called BOLTISE.md at the root of your project, next to server.cfg. The assistant reads it on every request, so it is where you record the things it cannot infer: which framework you are on, your folder conventions, naming rules, and anything it should always keep in mind.

BOLTISE.md
# This server


- QBox, with ox_inventory and ox_lib.
- Custom resources live in `resources/[custom]`, prefixed `srv_`.
- Never edit anything in `[core]` — those are upstream and get replaced.

Boltise also picks up rules files you may already have from other tools — .rules, .cursorrules, .windsurfrules, .clinerules, CLAUDE.md, GEMINI.md and AGENT.md — so an existing setup carries over.

Next steps

Section titled “Next steps”
Docs privacy