# Development install fails when running bin/rails db:migrate

**URL:** <https://meta.discourse.org/t/development-install-fails-when-running-bin-rails-db-migrate/332754>\
**Category:** Self-hosting\
**Tags:** dev-install\
**Created:** [October 25, 2024, 10:08am UTC](https://meta.discourse.org/t/development-install-fails-when-running-bin-rails-db-migrate/332754 "2024-10-25T10:08:46Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![nat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nat/32/235063_2.png) [@nat](https://meta.discourse.org/u/nat)\
**Post date:** [November 4, 2024, 8:57am UTC](https://meta.discourse.org/t/development-install-fails-when-running-bin-rails-db-migrate/332754/12 "2024-11-04T08:57:05Z")

</div>

I just came across this when creating a new local db and migrating.

Unfortunately I think it was introduced by [FIX: reset cache after flags are seed by KrisKotlarek · Pull Request #28801 · discourse/discourse · GitHub](https://github.com/discourse/discourse/pull/28801). Brand new migrations from scratch are not possible now.

@kris.kotlarek could you have a look please. I believe touching the redis cache in the initializer could be the issue.

---

_[View the full topic](https://meta.discourse.org/t/development-install-fails-when-running-bin-rails-db-migrate/332754)._