dalerka
25. Oktober 2017 um 05:38
9
Hmm… I reviewed the linked thread and seems like since 2014 the multi-core and multi-container setup is still quite questionable (pains vs. gains) and very use-case dependent. Thanks anyway, I’ll keep it simple.
you strongly recommend to separate containers, but can anyone explain a little more what happens if we don’t?
Not much happens, you just get slightly longer down times when you rebuild. Not that bad.
I would strongly recommend you run in a multicontainer environment if you are doing multisite , then use createdb to create the databases by entering the postgres container.
I’d really like to avoid having to run a multi-container setup as it doesn’t really have an advantage for me, and brings a lot of additional complexity (including having to migrate from my current setup).
One significant advantage, and why I think that it makes sense even for a single site, is that you can bootstrap from the command line without taking the site down for 5-15 minutes.
Bootstrapping has become such a rare event (thanks to Docker Manager) that this simply isn’t a strong enough argument to convince me to spend some hours adding complexity
Some time ago I had time to configure multisite with 3 containers: data, web, and redis. All was working fine until one day I upgraded, and bam, something wrong happened and I had to revert to single site from backups.
