> 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/resources-and-guides/configuration-and-updates.md).

# Configuration & Updates

Safe configuration practices and updating DrFx resources.

Use the configuration files supplied with each resource. Product-specific README instructions always take priority over general advice.

### Configuration basics

* Back up your current configuration before editing.
* Change one setting at a time, then test it.
* Keep valid commas, quotes, brackets, and data types.
* Do not edit escrow-protected files.
* Do not rename resource folders unless the README allows it.

### Updating a resource

1. Stop the server and back up the installed resource and configuration.
2. Download the latest release from the same delivery platform.
3. Read the new README or changelog before replacing files.
4. Preserve only settings that still exist in the new configuration format.
5. Replace the old resource files with the new version.
6. Restart the server and test the main features.

### Avoid stale files

Do not merge every old file into a new release. Old files can preserve removed code or outdated configuration and create errors that are difficult to diagnose.


---

# 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/resources-and-guides/configuration-and-updates.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.