Hi,
I'm running several blogs using S9Y on my server. Now I want to upgrade them to the latest version and switch them to a shared installation.
I already managed to create new blogs based on my shared install. Is there a way to convert an existing blog to a shared installation?
Best regards,
Stephan
Changing from local to shared install
-
stm999999999
- Regular
- Posts: 1531
- Joined: Tue Mar 07, 2006 11:25 pm
- Location: Berlin, Germany
- Contact:
I did this the last days.
A shared installation is different to a normal only in the php-files, not in the database.
So, I delete all php-files in my single installation, exception: the serendipity_config_local.inc.php because this has my blog-config. And I do not delete the folders archives, template_c and uploads.
Then I make the unix-links for htmlarea, plugins and templates (as you did it for your new shared installations, right?)
Then I copy the files from /deployment to the shared installation. You did this for your new blogs, too. Right?
And then, then I did nothing else - it was just simple. Perhaps you have to adjust the paths in the php-files (when you have to do so for your news shared blogs).
Because I have some own made templates on my further single installations, I had to copy these from there template-folder to the one new core installation. (before deleting this folder!)
Yet another thing: Are all these blogs for you? Because in this config every blog-admin can update Plugins in the core-installation (if spartacus is installed)!
So, if you want to share your shared installations to others, perhaps there must be a more secure installation like on supersized.org or so.
A shared installation is different to a normal only in the php-files, not in the database.
So, I delete all php-files in my single installation, exception: the serendipity_config_local.inc.php because this has my blog-config. And I do not delete the folders archives, template_c and uploads.
Then I make the unix-links for htmlarea, plugins and templates (as you did it for your new shared installations, right?)
Then I copy the files from /deployment to the shared installation. You did this for your new blogs, too. Right?
And then, then I did nothing else - it was just simple. Perhaps you have to adjust the paths in the php-files (when you have to do so for your news shared blogs).
Because I have some own made templates on my further single installations, I had to copy these from there template-folder to the one new core installation. (before deleting this folder!)
Yet another thing: Are all these blogs for you? Because in this config every blog-admin can update Plugins in the core-installation (if spartacus is installed)!
So, if you want to share your shared installations to others, perhaps there must be a more secure installation like on supersized.org or so.
Ciao, Stephan
-
clander
- Regular
- Posts: 8
- Joined: Sat Mar 11, 2006 7:15 am
- Location: Luton, Bedfordshire, UK
- Contact:
RE: Changing from local to shared install
Hi,
Once you have the deployment files, along with your serendipity_config_local_inc.php for each site in their directory, then it should work 'out of the box' for a simple shared install. If you are having difficulty getting your head around the idea, and how it could work, then start by creating a separate installation following the shared install instructions and copy over an existing config file from a live installation to see if it works.
There are also considerations on how much you will share with other installations, such as plugin/theme management, in each case the easiest way I have found to separate them is by creating suitable folders in the individual instances rather than linking to the serverwide shared directories.
A year or two back I wrote a series of scripts to assist with managing shared installations, primarily targeted at those with sysadmin rights, but you may find some of the ideas and output useful even if you don't have GOD access on your server. The scripts produce two files one of which is a Bash script to automate the copying and linking of files/directories, and the other is useful as an addition to the Apache webserver configuration.
You can find out more by looking at http://php-blog.cvs.sourceforge.net/php ... /s9y_conf/, and further information at http://www.labbs.com/~clander/s9y_conf/ along with http://www.labbs.com/~clander/s9y_conf/php/
Best regards
Once you have the deployment files, along with your serendipity_config_local_inc.php for each site in their directory, then it should work 'out of the box' for a simple shared install. If you are having difficulty getting your head around the idea, and how it could work, then start by creating a separate installation following the shared install instructions and copy over an existing config file from a live installation to see if it works.
There are also considerations on how much you will share with other installations, such as plugin/theme management, in each case the easiest way I have found to separate them is by creating suitable folders in the individual instances rather than linking to the serverwide shared directories.
A year or two back I wrote a series of scripts to assist with managing shared installations, primarily targeted at those with sysadmin rights, but you may find some of the ideas and output useful even if you don't have GOD access on your server. The scripts produce two files one of which is a Bash script to automate the copying and linking of files/directories, and the other is useful as an addition to the Apache webserver configuration.
You can find out more by looking at http://php-blog.cvs.sourceforge.net/php ... /s9y_conf/, and further information at http://www.labbs.com/~clander/s9y_conf/ along with http://www.labbs.com/~clander/s9y_conf/php/
Best regards
Chris Lander <http://www.labbs.com/>