The documentation of the sync gateway seems mainly focused around the config file setup. I am looking for a way to add databases to the config, without service interruption.
One way I’ve investigated was to use the admin rest API to create the database. This does work, however the added database doesn’t continue existing over a server restart. If the server is restarted, only the databases defined in the config file are retained, the other ones are forgotten.
This is different from the user data, which is actually persisted over server restarts, and thus not limited to the users defined in the initial config file.
How can I make it so adding a database through the admin API saves this to the config file of the server, or otherwise persists this information, so that a server restart doesn’t wipe de database config? Are there other solutions to manage the available databases on a live sync gateway cluster/server, without taking the service down?