> For the complete documentation index, see [llms.txt](https://saral.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saral.sunbird.org/dev-environment/maintenance-guide-for-saral-sand-box.md).

# Saral - Sandbox Maintenance Guide (Non-Prod)

Purpose - 

This guide is created to help teams to maintain sandbox in ready to use clean condition for the demo purposes.

1. Mongo DB collections clean up

During Demo large amount of sample data will be created which is no use post demo and to other demo users. Hence, it becomes necessary to clean such test data.  This is 2 step process where in first step current data will be deleted and in next step, fresh test data will be loaded for demo purposes. Please use below commands in sequence for clean up of data.

1.  To delete any old data from database run the following command in the VM where the sandbox app is installed. Execute below command in the terminal of your VM where docker is installed.

```
docker exec sandbox node ./data/import-data.js --delete
```

2.  To add golden data to the database run the following command in the VM where the sandbox app is installed. Execute below command in the terminal of your VM where docker is installed.

```
docker exec sandbox node ./data/import-data.js --import
```

2. Logging and Monitoring

Saral application stack has been enabled with logging and monitoring. Click [here](https://tekdi-docs.netlify.app/docs/learning/grafana/) for details on installation and setup guide

3. Click [here](https://docs.google.com/document/d/1T0x8RWGHxG578rytLDTivA1bducZYwUTl_VYwYLmLcs/edit#heading=h.q7kutkgpepnj) for troubleshooting guide on Docker and Docker Compose. This will also lists steps to check connection issue between Mongo DB and Backend Service.


---

# 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://saral.sunbird.org/dev-environment/maintenance-guide-for-saral-sand-box.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.