> For the complete documentation index, see [llms.txt](https://drfx-store.gitbook.io/drfx-store-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://drfx-store.gitbook.io/drfx-store-docs/documentation/support-and-policies/server-setup-checklist.md).

# Server Setup Checklist

A final checklist before testing a DrFx resource in production.

Use this checklist after following the product-specific README.

### Files

* The package was extracted completely.
* The resource folder is inside the server resources directory.
* The original internal folder structure is unchanged.
* No old release files were mixed into the new version.

### Dependencies

* Every required framework and library is installed.
* Dependencies start before the DrFx resource.
* Dependency versions are compatible with the resource.

### Configuration

* Required settings were reviewed.
* Syntax is valid after edits.
* No secret, license key, or credential was posted publicly.

### Server

* server.cfg contains the correct resource entries.
* The server was fully restarted.
* The first console error was reviewed.
* The main resource features were tested in game.
* Persistence was tested after another restart when the product stores data.

### Production advice

Test changes on a staging or development server before updating a live community server whenever possible.


---

# 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://drfx-store.gitbook.io/drfx-store-docs/documentation/support-and-policies/server-setup-checklist.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.