Is it possible, or has anyone tried this. I have root access to my server. I have a lot of installs in a lot of different urls/accounts.
Updating all the sites is a real pain.
Quesiton 1
I was wondering if I could put the core files above the root of each domain on my server and then just change the settings in each config file to point to the directory above all the different accounts so they could all share the same files.
I would keep uploads, and tmp folders in each site, and a config.php file and the index.php file all int he individual accounts, but I wonder if it would work if i put the admin, lib, and other folders/files above root that way when updates are needed, i could just update one file instead of multiple instances in multiple accounts all over my server.
Question 2, if this wont work...
How do you guys update the files in all your installs when security updates come out.
use one set of files for multiple sites
Re: use one set of files for multiple sites
thanks, but that is 3 domains pointing to the same cms, not 3 separate websites, different content, all using the same core files. thats a totally different idea.
I am tryig to run multiple sites using one set of core files, like editwrx or dragdropsitecreator or sitezen can do so we just have to update one install not tons of them.
I am tryig to run multiple sites using one set of core files, like editwrx or dragdropsitecreator or sitezen can do so we just have to update one install not tons of them.
Re: use one set of files for multiple sites
Multi *WEB-Site one installation
1st Problem is that you cannot be 100% sure the user will not change the files if they have Panel Access.
2nd If a module causes and issue everyone will have it.
Steps
Create symlinks via SSH for the directory or directories. (All will change when main installation is changed.)
3 Files will be changed
Create include/config.php (Specific to each site)
Change index.php (Specify location of config.php)
Change stylesheet.php (specify location of config.php **Only since 1.3.1)
When installation is done everyone gets the same Root config.php which they can copy and edit which has to be saved in /include/config.php
Each site has its own database. **Ensure users have backups automated to prevent problems when upgrading.
secure /include directory
User only changes database and /include/config.php
Multi-Domain One site simple Installation
http://forum.cmsmadesimple.org/index.ph ... #msg115404
1st Problem is that you cannot be 100% sure the user will not change the files if they have Panel Access.
2nd If a module causes and issue everyone will have it.
Steps
Create symlinks via SSH for the directory or directories. (All will change when main installation is changed.)
3 Files will be changed
Create include/config.php (Specific to each site)
Change index.php (Specify location of config.php)
Change stylesheet.php (specify location of config.php **Only since 1.3.1)
When installation is done everyone gets the same Root config.php which they can copy and edit which has to be saved in /include/config.php
Each site has its own database. **Ensure users have backups automated to prevent problems when upgrading.
secure /include directory
User only changes database and /include/config.php
Multi-Domain One site simple Installation
http://forum.cmsmadesimple.org/index.ph ... #msg115404
