currently there are two implementation for the database "behind": in memory or with postgres, both with zero config (except for starting an instance of postgres

currently there are two implementation for the database "behind": in memory or with postgres, both with zero config (except for starting an instance of postgres, in the second case!). it can be easily extended to use files as persistence, good idea :) regarding the pre-population, you can just make a quick script with curl that will add some data after you run the service. any thought?