# Data Model Sync

This can be used, for example, to develop a data model on a fylr staging instance and then transfer it to the fylr production instance.

## To use this service

1. Please create a support ticket:

* Tell us the name of the instance.
* Ask for a unique identifier, which will be used as the objectstore-ID.
* Tell us about the usage type of each instance using the same data model. Examples: production, staging, test. But you are free to choose any term.

2. We will then provide you with an objectstore ID and a string describing the instance usage. They serve to identify and allow access. Therefore we will make them into strings which conform to our syntax and may contain a part that is not easy to guess.
3. They must be entered into the fylr base configuration (frontend):

* `Server`: `https://schema.easydb.de/objectstore`
* `UID`: objectstore-ID
* `Instance`: instance-usage-string

Yes, "easydb" in the objectstore's store URL is correct. This will be changed at a later time to reflect the current product fylr.

If you setup a new fylr instance, the objectstore's configuration can be entered (initially only) in the fylr.yml, too:

```yaml
default_client:
  datamodel:
    uid: objectstore-ID
    server: https://schema.easydb.de/objectstore
    instance: instance-usage-string
```

## Other aspects

We decided to offer this service without a fee for now. We will reevaluate this based on the usage in the end of 2024.

Please let us know via support ticket if you have any questions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fylr.io/tutorials/objectstore.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.