was searching for an answer, but have only found fragments and no explanation (or i totally missinterpret what i have seen):
it seems elgg used to be multi-site ready - means, run different sites accessible with different subdomains or even domains all served from only one installed instance - but that feature was dropped from version 2 to 3.0, if i get it right.
We would want play such scenario: have/run different projects (each not seeing too heavy traffic), but representing very different communities, that needed their own domains .. and a reason not tackling it so far, has been the perspective being forced to install and maintain 3 or 4 independent instances.
Is it that elgg does not fit such a scenario? why was that feature then dropped? there must have been some good reasons for this decision ...?
would other projects/hosts see an advantage of such a feature or have other people earlier asked for it also?
would the elgg architecture allow the implementation of such a feature with reasonable effort ... that one could expect to see it with version 6.x?
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Nikolai Shcherbin@rivervanrain

Nikolai Shcherbin - 0 likes
- Robert Cooper@offternet

Robert Cooper - 1 like

- Nikolai Shcherbin@rivervanrain

Nikolai Shcherbin - 0 likes
- Robert Cooper@offternet

Robert Cooper - 0 likes
You must log in to post replies.Multisite for Elgg provided a single control panel for installing Elgg on your subdomains.
I think this plugin is no longer actual for Elgg.
Now you can easily do this with a set of tools from Docker, Vagrant, Ansible, etc.
Also, Elgg has no multisite feature since v3.
Look at our platform.
There we use (yet) the ability to run Elgg distributions on subdomains.
This is controlled by our custom plugin and scripts on the server.
So you can create something similar for yourself.
@RvR, I am posting here to allow continuity for others concerning multi-elgg site integration (your platform) and subdomain hosting of Elgg with just a single database which can only be done at a few Hosting Companies. As we know, each Hosting company has their own tools and the particular allowed hosting configuration options vary from Host to Host. The less expensive web hosting plans generally do not provide DNS Hosting configuration for subdomains which is needed for global DNS IP / nameserver for domains at remote domain registry company to be hosted on external hosting servers. However, I recently found Godaddy's Ultimate Plan (see image below) which provides all the tools necessary to install and configure DNS IP / nameservers to host domains to subdomains in cPanel (Godaddy went back to providing cPanel option to all hosting in 2023).
For less experienced users let me explain in more detail. All cPanel hosting allows subdomains to be created in some fashion. cPanel subdomain options in some cases is just a redirect from subdomain to a primary domain sub-directory. For example, the subdomain "john.domain.com" is simply redirected to subdirectory www.domain.com/john. In this example, John's subdomain "john.domain.com" is no more than just a cool url for john to share to the world to get to his Elgg build located in domain.com/john. This type of redirect does not provide configurartion for DNS Host Nameservers / IP resolution and therefore, John can not host a remote domain at subdomain "john.domain.com". However, if John had a way to configrue DNS Hosting "Nameservers and cPanel Server IP A Record, John could then host not only a remote custom domain but, he can also use subdomains to host multiple builds of Elgg.
Subdomains and databases: We are mostly instructed to use one (1) database per application and I support such recommendation as there are limitations on number of records; maximum simultaneous connections and data storage space limitations per each database instance, However, with Elgg where a total of 100 users average for 10 Elgg builds, all the builds could easy use a single database. Many Elgg installations can use the same database by simply using different database table prefix_. So John could use prefix "john_" or "mydomain_", for his own Elgg build and maybe use table prefix_ "tom_" for an Elgg install he is building for his friend Tom. This can all be done with 1 database hosting if subdomains can be created and the Hosting Company gives access to configure DNS Hosting settings for subdomains or at least subdomain "A Record (IP cPanel) & CNAME (subdomain options, mail, webmail, cPanel.admin, etc) configuration" for subdomains.
This is where Godaddy's Ultimate plan (very cheap - see image below) saves the day for Elgg subdomain hosting and provides the ability to configure DNS Hosting for subdomains. Godaddy has their own custom tool to Create DNS Hosting NAMESERVER addresses (2 each) for a domain NOT at Godaddy; "A Record" (cPanel / Primary Domain IP) as well as other subdomains like mail.john.domain.com for email use with John's subdomain. The Godaddy DNS Hosting tool allows for any domain name to be DNS Hosted to *.mycooldomain.com subdomain. provides and configure A Record IP and any CNAME subdomain setting desired. (I am still testing limitations of this hosting plan). Therefore, it is possible to host multiple Elgg builds on subdomains of the primary domain (i.e, john.domain.com, tom.domain.com, etc) and custom remote domain(s) hosted to subdomains as well.
Multiple Elgg administration without a single admin console is not ideal and can sure be confusing but, for experienced users having used cPanel "anywhere", can use cPanel at Godaddy as well. So migrating to GD will be an easy cost effective option, well, for those with cPanel experience.
This observation concerning possible Elgg multi-site administration comes from the Joomla multi-site administration plugin.
There are 2 strategies for a custom Elgg plugin to allow multi-Elgg administration:
1. Set the admin user login cookie the same for a selected Elgg installs. (A). All *.domain.com; (B). domain.com/*; (C). Enter path to each Elgg installations and (D). Validate user / password when both are true as listed in Admin Login Cookie. With this custom plugin option, the Admin can use Elgg bookmarks "private" to switch from site to site Admin Consoles.
2. Best case Elgg multi-site Administration for single Admin Console. Custom Plugin where using a single database (Alias could be used to external tables if more database space / connections are needed) and just like refreshing page in the browser, Admin would select Elgg Sites Administered List and data would be swapped in and out of Admin Console.
I would be willing to pay for either custom plugin development of 1. or 2. options above. (Just depends on cost and only if it could be used by public as well). Such a plugin my be in conflict with wzm.me offerings, if so, then no need for this custom plugin. I know how to do 1. above withe the cookie for my own use. There are browser extensions that allow cookie setting (not tested with Elgg just yet though).
Just wanted to remind that Elgg allows to manage cookies from the config.
Thank You for reminding me. I will examine code.
I have a hosting issue using just 7 elgg installations. My cpanel shows 150K files just for those 7 elgg installs. I scan the directories and only find about 70K files. Trying to determine if cPanel is giving wrong number for total files on server.
Roughly, how many files should their are used "at the hosting server" when a single instance of Elgg 6.x is installed ?