3 ms·
That's right. The server will be multi-tenant by default, unless you're a celebrity of some sort. Ghost is super fast, and under load you're mostly stressing ng
by sudhirj 6y ago
That's right. The server will be multi-tenant by default, unless you're a celebrity of some sort. Ghost is super fast, and under load you're mostly stressing nginx. I start with the bigger instances on AWS, and I've load tested them pretty heavily for multi-tenant.
Even with multi-tenant, each Ghost installation is its own version, own database and own settings, theme. So they're all independently configurable. I would like to move everyone through versions in lock-step, but I have no objection to letting people trigger their own upgrades (after I have the necessary automation in place).
- ayewo 6y agoI’m a bit confused by the opening sentence of your second paragraph. Perhaps we are using multi-tenant to describe slightly different things. A multi-tenant setup avoids the pain of maintaining multiple version in production. All multi-tenant customers are on the same server & db versions by design, so any future upgrades can be done for all customers at once. Also, upgrades are expected to be painless (at least in theory) since there is never more than one version in production. Customers with special needs are hosted as single tenant and of course you get to charge them extra $$$ for this special treatment.