On Wed, 09 Nov 2016 at 20:32:18, Mark Weiman wrote:
Adding support to DB.class.php to work with sqlite shouldn't be too difficult to implement. The only thing that would need to be decided is where in the config should the location of the database be. Perhaps if backend is set to sqlite, have it look for a location setting and ignore the rest?
It should be consistent with the way it is implemented in aurweb/db.py, i.e. only the name parameter should matter if backend is "sqlite".
Having this support sqlite would be very convenient as it means when working on the aurweb web interface, I wouldn't need to start a mysql service and could take the sqlite file around with me to make setting up a new instance easier.
Sounds good to me. Thanks for working on this!