On Discourse latest beta, docker install, multisite. Trying to restore a backup with original database REDACTED to current database db8015. Uploads end up in default, both on filesystem and in database. This happens both when the restore is triggered from the GUI, and when the restore is done on t…

Just to clarify, repro is: Create a multisite in a docker container Backup one of the multisites In a new docker container restore it Uploads are in the wrong place @kris.kotlarek can you repro this on local and see if you can fix it? I suspect we will be hit by this in future.

Only the destination container needs to be multisite to repro this. Create a forum in a docker container Create a backup In a new multisite docker container restore it Uploads are in the wrong place

I spent some time on this bug, and I wanted to update you with my findings. Basically, I confirmed everything you already said, the restore process is like that: migrate_database reconnect_database ... extract_uploads Problem is that after the migration task, reconnect_database is not switching to…

Are you sure that it is happening after the migration task? This code migrate_database puts "After migrate, before reconnect #{RailsMultisite::ConnectionManagement.current_db}" reconnect_database outputs this Optimizing site icons... Done After migrate, before reconnect default Reconnectin…

You are right. I removed Rake::Task["db:migrate"].invoke from restorer.rb and got correct database through the whole process. You are one step ahead of me, my plan now is to go into migrate task and see which step is breaking process. Thank you for pointing _dump, I will go directly there to see w…

I spent some time investigating that but finally I got a fix :slight_smile: https://github.com/discourse/discourse/pull/8218

Thanks! After giving this some more thought, what does it even mean when db:dump is ran on something which is not the primary database? Shouldn’t it just skip the db:dump command if database is not default?

Fixed was merged, thank you for finding that issue. That dump command was added because there was a problem with multisite migrations. I think that It shouldn’t matter which database we are using to dump structure because all multisites should have same structure.

Multisite restaura las cargas a 'default' en lugar del nombre real de la base de datos

Desarrollador

codinghorror (Jeff Atwood) 12 Octubre, 2019 22:10 2

¿Sigue siendo este un problema, @sam?

Tema		Respuestas	Vistas
Commandline restore specific site in multi-site configuration Support	2	715	12 Enero 2018
Rake multisite:migrate is broken Bug	4	1516	23 Junio 2020
Restore from old multisite installation failing Self-hosting	6	558	26 Agosto 2020
Restore to New Host Support	13	773	15 Enero 2026
How to specify alternate configuration in multisite Self-hosting	23	2518	13 Noviembre 2017

Multisite restaura las cargas a 'default' en lugar del nombre real de la base de datos

Temas relacionados