Closes #1224 It's unclear why we need to run migrations, since we're already calling [db:prepare][dbp] which does the following: > If the database exists but the tables have not been created, the command will load the schema, run any pending migrations, dump the updated schema, and finally load the seed data. See the Seeding Data documentation for more details. However, I found that calling `db:migrate` in the application template worked. [dbp]: https://guides.rubyonrails.org/active_record_migrations.html#preparing-the-database

Commits

Commits on Dec 5, 2024

Ensure bin/setup works

Ensure `bin/setup` works