As I understand it, ONCE makes it very easy to install/deploy web apps that use in-process database engines (e.g. SQLite). The installation of an app using Postgres is a bit more tricky -- the only way I can think of is running Postgres DB outside of the ONCE context and provide DATABASE_URL as env var to the application (after startup).
Question
Do you plan/would consider adding support for "managed" database? By "managed" I mean that ONCE runs a database server (just like it runs once-proxy instance), creates a new database and user for each application and injects database URL as env var (e.g. DATABASE_URL).
Don't take me wrong, I really like the way you handle the persistence layer -- quite elegant (I am working on the similar tool as ONCE and I did not think of SQLite as a solution to the persistence layer problem 😄 ). So I am just wondering what are you plans/thoughts in this regard.
As I understand it, ONCE makes it very easy to install/deploy web apps that use in-process database engines (e.g. SQLite). The installation of an app using Postgres is a bit more tricky -- the only way I can think of is running Postgres DB outside of the ONCE context and provide
DATABASE_URLas env var to the application (after startup).Question
Do you plan/would consider adding support for "managed" database? By "managed" I mean that ONCE runs a database server (just like it runs
once-proxyinstance), creates a new database and user for each application and injects database URL as env var (e.g.DATABASE_URL).Don't take me wrong, I really like the way you handle the persistence layer -- quite elegant (I am working on the similar tool as ONCE and I did not think of SQLite as a solution to the persistence layer problem 😄 ). So I am just wondering what are you plans/thoughts in this regard.