You can have as many different Mezzanine installations as you want.
Usually each installation is made up by:
- One virtualenv with Mezzanine and all its dependencies
- One database for the site
- Your specific projects files (settings, urls, custom apps; generated
via mezzanine-project)
Please note that this implies completely separate sites (database,
uploaded files, and code are not shared).
On the other hand, when the docs speak about multi tenancy they are
referring to using a single installation to serve multiple sites
(domains or subdomains). This means that with one virtualenv, one
database, and one settings file you want to serve multiple sites,
leveraging Django's Site Framework.
Here are some examples of when to use each approach:
- Separate Mezzanine projects: Use this if the sites you want to create
are completely unrelated. For example, if you want to host sites for
several clients in a single server, each client project should have its
own separate Mezzanine installation.
- Multi tenancy: Use this if a single project must be available through
different domains / subdomains. All sites will have the same set of
available apps and media files, but they can have a different appearance
and database records. For example, a school district may want to have
different sites for all their schools. They all share the same codebase,
but have a slightly different appearance and their own DB records (blog
posts, pages, etc).
Further reading:
- Django's site framework:
https://docs.djangoproject.com/en/1.10/ref/contrib/sites/
- Mezzanine's multi tenancy:
http://mezzanine.jupo.org/docs/multi-tenancy.html
- Deployment tutorial which mentions multiple projects in a single
server (note that this assumes Mezzanine is being deployed to a VPS)
http://mezzanine.jupo.org/docs/deployment.html#tutorial
Hope that clears things up a little bit :)
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
