Hello All,
I now work with drupal approximately 1 year and really like the CMS system, i'm starting a small company with a friend and we are going to deliver simple small sites for restaurants/health shops/gymes just "the small companies" around the corner.
I was reading about Multisite and found this interesting, because this way i don't need to check/update all the CMS systems when there is a Security Update.
But after reading, i found multisite has his downsite: "less secure". I now run my own VPS and every domain has his own user, that way nobody can hack the other site when it gets hacked (somehow). The only one who has access to admin rights is me and my friend.
Would it be better to just run every site on it's own? Also some sites need different modules then the other (i think)
I was just wondering what your opion is? I read there are options to make it more secure, but I first need to investigate this...
Would it be a good approach to run Multisite, but with a different theme/content for all the sites we develop?
Comments
I think you are
I think you are misunderstanding what multisite means; or perhaps I'm getting your meaning wrong.
Multisite is basically a way to use the same basic code base for multiple sites. Imagine you create a basis setup for restaurants that include different features. Each site will have its own db and files directores but they will share a single codebase means you can maintain it (=code) all in one place. That does not mean you only need to run update.php once. When you add or update any modules or core, you'll need to update all the sites since updating is updating your db too. Also I don't see any inherent security issues beyond normal sites/server with a multisite setup assuming you are doing everything normally. If you want to take multisite setup to the extreme and are managing a bunch of sites, I recommend checking out Aegir setup.
Is multisite ...
Hi :
When you build a multisite you create a folder under sites folder. If you wanna use other modules or themes besides the core o main site you just create folder modules and themes and you put there the modules or themes you need to the new site. That's all.
There is gonna be a webseminar in https://acquiawebinars.webex.com/mw0306ld/mywebex/default.do;jsessionid=WnF5PvdJT8ryQQPf8QMv40Y0WqYPYcB5prqFZClmQ4Ftql2FVQh0!360491697?nomenu=true&siteurl=acquiawebinars&service=6&rnd=0.655361072706981&main_url=https%3A%2F%2Facquiawebinars.webex.com%2Fec0605ld%2Feventcenter%2Fevent%2FeventAction.do%3FtheAction%3Ddetail%26confViewID%3D280277830%26siteurl%3Dacquiawebinars%26%26%26 to talk about security. You can register.
Regards,
Manuel
In most cases I would
In most cases I would recommend you different installations for each site. You should drush (http://drush.ws) to manage these sites.
The problem is: Imagine you have different customers with different module combinations on their sites. There are some modules working with other modules in a special release combination only. If you now update the multisite installation you will do good for one customer but you will wreck the other customers installation.
If you have a system like drupal gardens where you provide a fixed module set for your customers without the dependencies I was talking about go with multisite and you live will be easy.
Remember: I compute you!
@rogerpfaff Can you give a
@rogerpfaff
Can you give a scenario of these 'co-dependent' modules that can cause a site to crash? Unless you're using Dev versions and don't run update, I can't imagine when that would happen--but would like to understand Drupal better.
There are advantages and
There are advantages and disadvantages to all setups..
Multisite functionality is great and useful but you have to work out if its going to work for YOU.. Everyone's requirements are different..
My setup is sort of half way between the two..
I have a "core" directory with all the Drupal files.. I have a vhosts directory for each site.. In the vhosts directory I symlink to the core version I want for that site and I created the /sites/* directories within the vhosts directory.. This means I have a shared codebase but a complete install in each vhost directory that could be copied out if needed.. Also I can then manage the upgrade of a new core version.. I put the new core into the "cores" directory and then change the symlinks for the site I want to upgrade.. Obvioustly the directory structures are all the same so its easy to script upgrades for all sites once the new core version has been fully tested on a couple of sites..