per Eli's suggestion, initialize the DB in a task that runs only on actual startup after all classes have registered themselves
per Eli's suggestion, initialize the DB in a task that runs only on actual startup after all classes have registered themselves

this also tries to initialize the DB, and if it fails, retries 10 times with a 5 second delay, to deal with the database not being ready to accept connections (this happens with docker containers starting up for the first time, and out of order)

magfest/ubersystem,RAMSProject/rams,md1024/rams,RAMSProject/rams,md1024/rams,magfest/ubersystem,magfest/ubersystem,migetman9/ubersystem,migetman9/ubersystem,md1024/rams,migetman9/ubersystem,RAMSProject/rams,magfest/ubersystem