Hello,

I am new to Linode - but so far I like what I see .

What I would like to do is to create a pre-set configuration of Wordpress that I can use as a base for all future Wordpress installs. In other words, I want to install my base themes, plugins, permalink settings, etc. I then want to clone that installation of Wordpress so that I don't have to set all that up each and every time. I am wondering what is the best way to do this - both conceptually and technically:

Here are the ideas I have thought of:

ONE DISTRIBUTION - ONE USER - MANY SITES
../USER/public_html/DOMAIN1/
../USER/public_html/DOMAIN2/
../USER/public_html/DOMAIN3/



ONE DISTRIBUTION - MULTIPLE USERS - ONE (OR MORE) SITES PER USER
../USER1/public_html/DOMAIN1/
../USER1/public_html/DOMAIN2/
../USER2/public_html/DOMAIN1/
../USER2/public_html/DOMAIN2/
../USER3/public_html/DOMAIN1/
../USER3/public_html/DOMAIN2/


MULTIPLE DISTRIBUTIONS - ONE PER CLIENT or ONE PER SITE
In this situation I clone an existing distribution with my particular wordpress configuration for each client or perhaps per each site.

Connected to this question is also ease of updating the sites. I plan to update both Wordpress and the plugins/themes for my clients. I want to automate this process as much as possible. In other words, I don't want to have to update each and every installation/plugin individually. I want to be able to do this globally for all of my installations at one time.


Now - as far as I understand - there are two ways I can accomplish the installation. I can copy the files and database - this works for the One Distribution - multiple users and/or sites option listed above. Aternatively, I can clone a linode [I don't really know anything about this - but I read on the forum that something of this nature is possible]. I am wondering which method people think is better and any issues or concerns I should be aware of. I am also interested in any other options and/or methods that I haven't considered.

In terms of updating - I have read this article: http://www.devlounge.net/code/bash-scri ... ress-blogs. Perhaps this is the best way to do it - but I don't know (never done this before) and I'm wondering if there are other suggestions and whether or not this method can work with multiple distributions.

I thank you in advance for any help you can offer.

Thanks and be well,

Moshe

Why don't you just use the built-in multisite feature of Wordpress?

It definitely has built-in features to support a network of sites.

I agree with akerl the multi site feature introduced in wp 3.0 is a darn sight easier than rolling your own solution. I use it and it works.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Hi there,

Thanks for responding.

There are two main reasons why I don't want to use multi-site [I actually had a third, but I forgot it] ]

1) With multi-site I can't give my clients Buddypress. I can basically have one Buddypress installation per Wordpress installation - I can't give it to my subsites. I want to be able to offer my clients Buddypress.

2) User login is logged for all sites. Let me explain what this means. If I signup for one subsite with the following email address: myname@myemail.com and then I try and signup for a different subsite on with the same email address it will tell me that that email address is already taken. Now, these two may be from two different clients and that could cause user confusion.

The bigger of the two issues for me is the Buddypress, but the second issue illustrates to me that there are various issues with multi-site that could come up that I don't want to have to deal with.

With that said - does anyone have any advice on my original question?

Thanks and be well,

Moshe

You can install BuddyPress on single or multi WordPress, that is not an issue. You are correct that their is only one user table for a MU installation. So for distinct user bases the easiest route is distinct single WP installations.

Rolling out a WP installation is more than just installing some files. There are webserver and database configuration issues to consider (amongst others) that are too broad to answer.

Perhaps you can install some plesk/webmin like server management tool that will allow you to do these things, but it is unlikely that you will find a 'complete bundle' that just happens to fit your requirements.

Looks like it is time to dive in and get your hands dirty - build your own!

Thanks graq for your response.

I would like to point out that I have already figured out what and how I want to configure Wordpress. All I want to know is what is the best way to add clones of my basic configuration. I appreciate all of the advice, but I really just want to know an answer to my original question.

So - any ideas out there?

Thanks and be well,

Moshe

His point is that what you're trying to do is multiple orders of magnitude more complicated than you seem to grasp. The vision you seem to have, where you have a "master" wordpress copy, which can be simply copied to a new location in a tree of users or domains, and function as a new and unique wordpress install, would not work.

You would be looking at an enormous undertaking of work to build a configuration and deployment tool that would automate the process of configuring new wordpress installs, setting up the necessary resources, and deploying them. So unless you're looking to invest large amounts of time creating a triangular wheel, I'd recommend learning how to use a round wheel (Wordpress networks) to your advantage.

Once again, I appreciate everyone trying to help me out here.

I would just like to point out that I did not come to this question lightly - I have a good deal of experience with WPMU/Multisite and have been working on my particular project for a long time. I know what I am trying to accomplish. All I want is an answer to my original question [when I asked for other suggestions, I meant other suggestions for how to accomplish cloining of individual Wordpress installs].

So - one last time - does anyone have any advice on my original question of how to set up multiple version of Wordpress installations that do NOT involve WPMU?

Thanks and be well,

Moshe

If no one here knows, it looks like there's a WordPress forum that might yield better ideas. I'm assuming the answer is going to be more complicated than "copying the files and running some install script," but... well, try copying the files and running some install script?

_________________

/* TODO: need to add signature to posts */

Hi there,

I know that I can clone a Wordpress install by copying the files and database. I'm asking my question from a server point of view - which I have less experience with.

Thanks and be well,

moshe