Multisite in diferent Cpanel accounts?
I wonder if it is possible (or not) to do a multisite install, but without share the same cpanel (or host accounts)
In other words, if you follow instructions like these (http://drupal.org/node/348619#comment-1265617), with parked or addon domains, you get a multisite drupal installation (great!), but if you want give all the owners of the domains a Cpanel account, you can NOT do it, because is the same Cpanel account (you can access it throw the diferent domains, but once inside Cpanel, you can manage all of them).
I'd like to have a multisite Drupal, sharing the code, but not DDBB nor contents, but I'd like to have different and separated Cpanel accounts. Is it possible?
Regards
Groups:
Login to post comments
I have been trying to do
I have been trying to do this for quite a bit of time now.
The major problem that there is with this is permissions. The user that owns account 1 does not have permission to see or execute the core php files, wither you store them in a "shared" folder or put them in account 2 public_html.
I have tried many many different ways to do this and they have all failed. Now, I believe anything is possible and that if someone had a dedicated server with whm/cpanel installed, they could configure the permissions so this might work. However trying to get this to work with a reseller account just wasn't happening.
This person (http://groups.drupal.org/node/18092) claims he has accomplished this with Webmin and Virtualmin (which are open source analogs of cPanel and WHM, respectively) however, I don't believe he has published a how to yet. Plus this would also require you to have your own dedicated server or VPS.
I believe the only alternative to this if its just not possible due to permissions, is to create an UI rich cPanel api that would give users the ablitiy to manage their emails, and admins the ability to track and cap bandwith and diskusage, which is really the only reasons we want to give them cpanel access.
I do have a dedicated hosting account . . .
and I need separate cpanel accounts so we can have separate disk and bandwidth quotas. Each site is a different domain, though we might want to add subdomains on to some of those domains. our hosting service uses whm and cpanel. I'm also no sysadmin and need to focus more on the drupal side - site content, configuration, and functionality.
Any tutorials that I missed on how to do this? Any help would be greatly appreciated.
Drupal install above the root
I am currently setting up a LAMP VPS with WHM/cPanel for hosting Drupal sites and am looking for the same thing.
This guy is talking about having the core Drupal install above the root of the web space for better security.
http://justinhileman.info/articles/a-more-secure-drupal-multisite-install
I'm wondering whether I can put the Drupal core above all of the accounts and have links to it.
I haven't tried it yet but this is my next goal. Am posting to stimulate the discussion.
Regards
Geoff
That guy's article is
That guy's article is entirely the wrong way to do Drupal multisite, and it's all done under incorrect assumptions:
Assuming the web server is properly configured enough to run Drupal in the first place, it's immaterial, because nobody will be able to view the files which have configuration info in them, and they won't be able to do anything if they hit the install script anyway, assuming Drupal's already installed.
He hacks core. He must have fun re-doing all those hacks every time he upgrades core.
Please ignore that article entirely.
Has merit - Code base is above the root and he doesn't hack core
This topic is exploring the possibility of having a multisite Drupal installation where each of the sites have a seperate cPanenl account. The only way (I can see) to do that is to have the core Drupal code above all the cPanel accounts and have the site specific files in the cPanel accounts using the one Drupal code base.
In this article the author has a multisite setup where the core code is above the root folder which is part way to where (I think) we need to go.
Is he describing a standard multi site set up? No.
His three reasons for doing this are
1. Files uploaded to one domain will only be accessible to that domain.
2. Configuration and install files won't be accessible to the bad guys so you can sleep better at night.
3. Third party software installation in a subdirectory will only be accessible to that domain
I agree with your point that his second reason is not that important but that is not why I am interested in his article.
No where in his article can I find any reference to him changing any core files. He uses simlinks and php files in his site folders that include the essential core files so each site can use the one code base. These do not need to be changed when Drupal is upgraded. So an upgrade is the same as in a standard Drupal multisite setup.
Regards
Geoff
You're right, he's not
You're right, he's not hacking core - I misread what he was editing when I was skimming over the article. My bad.