Development install fails when running bin/rails db:migrate

nat · November 8, 2024, 1:43am

Thanks for the report @NateDhaliwal

Kris fixed the issue with

github.com/discourse/discourse

FIX: setup with db:create db:migrate (#29609)

committed 04:06AM - 06 Nov 24 UTC

lis2

+8 -2

After data seed, we should reset Redis cache to ensure that the correct flags ar…e cached. However, `db:create` is skipping Redis https://github.com/discourse/discourse/blob/main/lib/tasks/db.rake#L39 And uses `ActiveSupport::Cache::MemoryStore.new` https://github.com/discourse/discourse/blob/e2292d4c5914875ad0e303770c56db7cc96847e3/lib/discourse.rb#L523 Therefore, the reset flags cache was moved to initializers and evaluated only when the cache is Redis and Flags table already exists. Meta: https://meta.discourse.org/t/development-install-fails-when-running-bin-rails-db-migrate/332754

We should be good now!

Topic		Replies	Views
Db:migrate fails (1.5.4 to 1.6.4) Support unsupported-install	10	1355	October 1, 2016
Help! Upgrade led to complete fail Installation	8	1279	March 9, 2021
Update failed due to primary key sequence error Installation	7	1378	August 12, 2017
Vagrant based server failing on db:migrate Bug	9	3270	February 20, 2017
Failed to bootstrap / rebuild fail on stable branch Bug	8	736	December 31, 2022

Development install fails when running bin/rails db:migrate

Related topics