Deployment

[isedwards]

api.climsoft.org (13.41.215.201)

Demonstration api used by demo.climsoft.org application

• By default, two named databases should be available in the demonstration database and the user will be able to select which to use in the demo app: test-database and empty-database
• Both databases should be non-persistent - their contents should be restored to default after X minutes.

api-prod.climsoft.org (18.169.81.197)

This api will be used by the app.climsoft.org web application.

• The main production database must be persistent with no chance that it could be restored to default after X minutes.
• The database server will contain many named databases
• There should be a method to backup databases

Note: gaining access to climsoft.org DNS will take a few days. In the meantime we can set up api and api-prod at the openclimate.net domain.

[faysal-ishtiaq]

TODO:

• write a script to install docker and docker-compose
• write a script to restore databases to the original stage
• write a cron job to restore db at X minutes interval

[faysal-ishtiaq]

@isedwards

There should be a method to backup databases

I have investigated a little bit into this. There are several ways to take backup which are described here:

• https://mariadb.com/kb/en/backing-up-and-restoring-databases/
• https://hub.docker.com/_/mariadb (section named "Creating database dumps" onwards)
• https://www.youtube.com/watch?v=dQRuK7y2zuc

To summarize, there are two tools called, mariadbdump and mariadb-backup.

mariadbdump takes a logical backup and stores the data in an SQL file. The restoration process is straightforward. Just need to execute the SQL file. But it takes more time than restoring physical backup.

mariadb-backup takes logical backup and stores the data in a directory. There is an additional prepare step which can be done either at backup or restore time. Takes less time than logical backup.

Which type of backup do we want? And where do we want to store the backups?