IMO while settings-in-sqlite is maybe cool, operationally it's more trouble than it's worth if someone wants to make a production deployment--they now need to either copy around this database blob, or have some setup script that runs sqlite3 queries to insert their config.
Might I suggest scrapping that idea entirely and doing something less crazy like configuration-from-environment?
IMO while settings-in-sqlite is maybe cool, operationally it's more trouble than it's worth if someone wants to make a production deployment--they now need to either copy around this database blob, or have some setup script that runs sqlite3 queries to insert their config.
Might I suggest scrapping that idea entirely and doing something less crazy like configuration-from-environment?