You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Include these options will let you tailor the output:
--skip-db to skip DB setup --database=sqlite to use an sqlite database (the default) --database=postgres to use a postgres database --database=mysql to use a mysql database
The text was updated successfully, but these errors were encountered:
How committed to postgres being the default database are you? SQLite is much simpler due to it being file-based, plus there's a growing movement of using SQLite in production so it's not setting people up for failure.
We can turn strict_tables on and generally optimize SQLite in other ways too rails/rails#49349
@cllns Yeah, I'm happy to switch to SQLite as a default. It would make the first-run experience much simpler.
I don't personally have an appetite right now for figuring out all the ways we should tune SQLite for best performance for web-style apps. If you could help figure out a minimal set of things we could do there, that'd be very helpful. Otherwise, we can just live with the defaults and consider improvements in future releases.
Yea I'm definitely down to figure that out and set up some solid defaults.
FWIW, I think Hanami and SQLite in production may be a particularly good combination since Hanami is so fast and memory efficient. One big server can probably handle a ridiculous amount of traffic. Time will tell!
Include these options will let you tailor the output:
--skip-db
to skip DB setup--database=sqlite
to use an sqlite database (the default)--database=postgres
to use a postgres database--database=mysql
to use a mysql databaseThe text was updated successfully, but these errors were encountered: