> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/setup/install-works/system-data-setup.md).
# System Data Setup
Before you run the Works application, you need to set up the basic system data such as boundaries of the geography and the master data. In this document, we will illustrate the steps to load the base data for the server.
1. Create a superuser by using the super\_user\_createion curl given in the collection.
{% file src="/files/dPZTG9Wy8EmXyL77Wdeo" %}
2. Add Master data by port-forwading the mdms-v2 service and creating the schema present in the collection. Once all the schema is created add the seed data according to requirements.
{% file src="/files/vEUHKrHPK1W05ZdbBm5E" %}
3. Once the master data is set up send the request to the workflow service to create the workflows for the services which require workflows as mentioned in the collection given below.
{% file src="/files/oXKVQcvxJMETxk4jdC5V" %}
#### 4. Enable File Store
* Encode Aws access key and secret key to base64 encoding
```
echo -n "" | base64
```
* Update the secrets in the cluster (\*do not put these in the git DevOps repo files and commit)
```
kubectl edit secrets egov-filestore -n egov
```
* If it is not editable by the VI editor, we can use vs code to edit the file, run the below command and run the above step again
```
export EDITOR='code --wait'
```
#### 5. Redeploy Services at once to read from new data
* Run the below command to delete and restart all the services
```
kubectl delete pods --all -n egov
```
* Run the command below to check if all pods/services are running. If not, wait for some time and check again:
```
kubectl get pods -n egov
```
---
# 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.digit.org/works/setup/install-works/system-data-setup.md?ask=&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.