Verify that init-db actually loads backups when present

[bleucitron]

Currently, the code looks exactly the same:

                    .then(function(){   
                        if (!process.env.BACKUP) {
                            console.log('no backup file');
                            generateDefinitions()
                            .then(function(){
                                console.log("Dropped and created the tables.");
                                resolve();
                            })
                            .catch(function(err){
                                console.error("Couldn't write the schema", err);
                            });
                        }
                        else {
                            generateDefinitions()
                            .then(function(){
                                console.log('definitions generated');
                                resolve();
                            })
                            .catch(function(err){
                                console.error("Couldn't write the schema", err);
                            });
                        }
                    })

[vallettea]

at this level yes because there used to be a call to hardCodeSensors when no backup was specified.
The use of the db file is in createTables.js

[DavidBruant]

The use of the db file is in createTables.js

Ouch. Not a good idea. createTables should just create the tables. Other functions should be created to deal with backups (and maybe other tools to combine them both).

[vallettea]

I agree, but sometimes you write code that works and does the job and move on, leaving the code where it was written and tested...