Hello,
This is a small service designed to solve the configuration problem of anything. More specifically, the configuration of something connected to the Internet, which can be represented as a fairly branched object, delivered in the form of JSON.
Problem
Programs need to store and use a variety of data, known as “settings,” or “configuration.” What is this data?
')
- they are not very well structured
- not very many, often no more than a hundred values
- they need to be given to edit ("admin interface")
- The application must be aware of the changes.
What can we think of for this, and why is it not suitable?
- Relational base. The tabular structure is unsuitable for placer unbound data. The interface is missing.
- Store the installation along with the code. The structure can be any, but the user interface will be a conversation with the developer.
- Store the settings in a text file. A variation of the previous approach. Try to teach a normal person to edit YAML.
- Use a third-party service like Google Data API. It will work, but the overhead will be terrible, and the speed of the turtle.
Actually, the service.

Simple logic of work:
Register, choose a free name for the scheme (this is called "seed"). Names are common to all, as they will be subdomains. We fill the circuit with contents in the form designer:

For each value, select the type, the field name, and what will be on the screen in the edit form.
Automatically obtain one instance of this scheme (each one is a “tree”) called main. You can do several, for example, for tests or development environment. We assign a password for each tree.
The data of each hypostasis is available to a person, for editing, at https: // <schema name> .config.ly
- login: the name of the hypostasis ("main" if you have not changed anything)
- password: the one you specified in the configuration.
Since you are too lazy to create your own scheme (I would be), and you want to see the interface, you can go to the finished one:
Data is also available for reading to a soulless bot via HTTPS GET
api.config.ly with Basic Authentication:
- username: schema name
- Password: API key that was generated for the tree, and which can be viewed when editing the schema.
And again, you can immediately try:
curl -k -u primer:yV7mkhNRs00tM2nTdKuEWV2a api.config.ly
Total
What have we got? Just storage of JSON objects to which the minimal convenient editing interface is attached. Perhaps this will save you from writing the next admin panel.
Feedback and constructive criticism are accepted with gratitude.