> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v2.0/technical/guides/installation/opencrvs-maintenance-tasks/resetting-a-server-environment.md).

# Resetting a server environment

### Before you begin

The **Reset environment** Github Action can be used to clear a **development,** **qa and staging** environment of all data. This is useful during testing of environments where you may have made test registrations.

{% hint style="info" %}
After resetting your environment, it contains no data at all. It must be seeded again
{% endhint %}

### Run "Reset environment" workflow

{% hint style="danger" %}
Before resetting production environment make sure you have working backup of your data.

In default configuration GitHub action will require at least 3 approvals for Production environment reset.
{% endhint %}

1. Navigate to GitHub Actions within `infrastructure` repository
2. Select "Reset environment" action
3. Select "Target environment" from dropdown menu, all environments created in the [Create a Github Environment](/v2.0/technical/guides/installation/deploy-set-up-a-server-hosted-environment/create-a-github-environment.md) step, should be listed here.
4. Click "Run workflow" button


---

# 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://documentation.opencrvs.org/v2.0/technical/guides/installation/opencrvs-maintenance-tasks/resetting-a-server-environment.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.