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
I need help with install Installation	9	202	November 7, 2024
Rebuilding failed 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 4979 exit 1> Installation	8	1901	March 8, 2021
Help! Upgrade led to complete fail Installation	8	1293	March 9, 2021
Failed To Bootstrap Pups::ExecError 'bundle exec rake db:migrate' failed with return exec failed with the params 2.9.0.beta4 to 2.9.0.beta5 Installation	7	1349	June 20, 2022
Upgrading 2.7 to 3.1 failing: "hotlinked_media_status" already exists Installation	30	1107	October 1, 2023

Development install fails when running bin/rails db:migrate

Related topics