> For the complete documentation index, see [llms.txt](https://docs.limescripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limescripts.com/documentation/installation.md).

# Installation

This is the general workflow. Instructions supplied for a specific resource take priority.

1. Back up your server files and database.
2. Check the product listing and included documentation for dependencies and compatibility.
3. Extract the resource into your server's resources directory. Preserve its original folder name unless its instructions allow renaming.
4. If the release includes database migrations, review and apply the documented migrations to the correct database after backing it up. Not every resource requires SQL.
5. Edit the documented configuration files for your server.
6. Start the required dependencies before the resource in server.cfg.
7. Restart your staging server and review the server console and client F8 console.

Example only—replace the placeholder with the actual resource folder name:

```cfg
ensure your_resource_folder
```

Avoid importing the same SQL repeatedly or starting multiple copies of a resource. Test permissions and the main player flow before opening the server.

[FiveM resource basics](https://docs.fivem.net/docs/scripting-manual/introduction/introduction-to-resources/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limescripts.com/documentation/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.