GoFuckYourself.com - Adult Webmaster Forum

GoFuckYourself.com - Adult Webmaster Forum (https://gfy.com/index.php)
-   Fucking Around & Business Discussion (https://gfy.com/forumdisplay.php?f=26)
-   -   Multiple wordpress blogs on one server (https://gfy.com/showthread.php?t=689451)

alexg 12-23-2006 02:32 PM

Multiple wordpress blogs on one server
 
What is the best way to handle multiple (say 20-30) blogs on one server?
each blog is on a seperate domain...

should I use a seperate mysql database for each blog?
several blogs on one database with a defferent prefix for the tables of each blog?
does it even effect the speed of pageload? what would you recomment to do?

FunkyDog 12-23-2006 02:34 PM

I would just create a database for each blog. I think that would be the safest and the fastest :2 cents:

TheSenator 12-23-2006 02:37 PM

KISS Keep It Simple Stupid

alexg 12-23-2006 02:41 PM

Quote:

Originally Posted by TheSenator (Post 11581117)
KISS Keep It Simple Stupid

:1orglaugh

but the question is what would 'simple' be?

for me the simplest is to make one database and just use a different prefix for each blog...
but is it a good way, or is it better to make a seperate database for each blog?

Pimpin_J 12-23-2006 02:46 PM

For each his own :)

Agent 488 12-23-2006 02:48 PM

Quote:

Originally Posted by alexg (Post 11581133)
make a seperate database for each blog?

that's what i do - no issues so far.

NdO 12-23-2006 03:05 PM

Use mu wordpress :)

DjSap 12-23-2006 03:18 PM

You could give wordpress mu a try or lyceum, however I would recommend having seperate DB's for the installs in case you ever decide to sell some blogs...

ROBO2017 12-23-2006 04:00 PM

If they’re for spam I don’t know. But I consider each domain a separate property.


Robo

Mike Semen 12-23-2006 04:02 PM

I am personally much happier with seperate DBs for each site. Especially for backups and stuff.

I only have one instance of 2 sites, 1db and that's for subdomains on one site.

baddog 12-23-2006 04:07 PM

20-30 blogs - 1 db should be fine

200-300 blogs . . . break it up a little

scouser 12-23-2006 04:18 PM

Yeh, seperate dbs for each installation is the best tbh.
Also, btw if your host uses a nice interface, there is probably an easy to use installation thing. Like the fantastico thing within cpanel often, or the dreamhost one click installs. Saves quite a bit of time. I do that all the time, and i have a folder of plugins, just copy that across.

alexg 12-23-2006 04:25 PM

thanks for the input so far guys...

looks like baddog is the only one so far who suggests using one db for 20-30 blogs...

i guess i will use one db for every 5-6 blogs or so, and thus a total of about 5-6 db's for my project...

StarkReality 12-23-2006 04:26 PM

I see an advantage in having a seperate database for every blog. If you mess up your database for whatever reason (or someone else does), it will only affect one blog. Performance wise, it won't matter much if everything is on one server anyway.

If you have hundreds of blogs, having 10 in one database for a better overview certainly won't hurt, just don't put all your eggs in one basket...I follow this rule for everything: Hosts, sponsors, databases, etc.

Agent 488 12-23-2006 04:29 PM

Quote:

Originally Posted by alexg (Post 11581720)
thanks for the input so far guys...

looks like baddog is the only one so far who suggests using one db for 20-30 blogs...

i guess i will use one db for every 5-6 blogs or so, and thus a total of about 5-6 db's for my project...

where do you host - i have some of my blogs on dreamhost and is super easy to create new db - no point not doing it ...

RF_Erick 12-23-2006 06:09 PM

Quote:

Originally Posted by StarkReality (Post 11581732)
I see an advantage in having a seperate database for every blog. If you mess up your database for whatever reason (or someone else does), it will only affect one blog. Performance wise, it won't matter much if everything is on one server anyway.

If you have hundreds of blogs, having 10 in one database for a better overview certainly won't hurt, just don't put all your eggs in one basket...I follow this rule for everything: Hosts, sponsors, databases, etc.

I agree.. It would suck to mess them all up because of 1 error.

baddog 12-23-2006 06:49 PM

Quote:

Originally Posted by alexg (Post 11581720)
looks like baddog is the only one so far who suggests using one db for 20-30 blogs...

ummm, I did not suggest shit, I said 20-30 blogs - 1 db should be fine

I have clients with 1,000's of blogs . . . I observe what they do, and what causes issues and what doesn't.

If you are only going to have 20-30 blogs go either way.

kuthi123 12-23-2006 07:05 PM

i personally have 3000 wordpress blogs in one server.All of them having separate mysql table.so 20 -30 blogs is fine.

tombarr 12-23-2006 08:40 PM

Quote:

Originally Posted by alexg (Post 11581720)
thanks for the input so far guys...

looks like baddog is the only one so far who suggests using one db for 20-30 blogs...

i guess i will use one db for every 5-6 blogs or so, and thus a total of about 5-6 db's for my project...

Did you really want advice on which is the best way or did you want someone to tell you what you were already thinking?

You asked advice on the "Best" way to handle these blogs, but by your reply here it seems you were really seeking validation for the method you already had in mind.

The "Best" way to handle them depends on what you plan to do with them in the future.

One DB can be dangerous.

Separate DB's provide more flexibility and protection in the event of any failures.

Server DB's and Wordpress installs are so easy to do and almost fully automated, I would not do it any other way just for the protection it brings.

Also, on any website network, having different class C Ip's for each domain is a good idea. Many dedicated hosting companies can offer you a range of Class C IPs. You should check into it. It will give your network more credibility with SE's.
:2 cents:

alexg 12-24-2006 06:22 AM

Thanks again guys...

To sum it up, no i wasn't looking for a validation to what i'm already doing.
I host with webair and yes, it's easy to create new databases, it's not a big issue...
I'm aware of the class c issue and I do have different ips for each domain.
the only thing I wasn't sure is if it matters performance wise whether I use one DB for each blog or several...

More Booze 12-24-2006 06:46 AM

You'll be fine with 1 DB for 20-30 blogs.

eMonk 12-24-2006 06:55 AM

i also would like to have multiple blogs on one server but never done it before. what kind of hosting package would you need? i have the webair starter package now at http://www.webair.com/host_virtual.htm. will this package beable to handle 2-3 small blogs?

Adultnet 12-24-2006 07:02 AM

Quote:

Originally Posted by baddog (Post 11581585)
20-30 blogs - 1 db should be fine

200-300 blogs . . . break it up a little

you should be fine using only one database and different names for the table's anyways its more about your server and how much visitors can the box handle if the server won't do good you might go and use anther database.. its really not needed from the point of the speed point HOW ever you might want to split this to different database to make it more easy for yourself to manage.

Scottish Guy 12-24-2006 07:02 AM

Wordpress blogs are over saturated they are everywhere

Sosa 12-24-2006 07:10 AM

Quote:

Originally Posted by Scottish Guy (Post 11585878)
Wordpress blogs are over saturated they are everywhere

and they also make money

DaddyHalbucks 12-24-2006 07:52 AM

I have them all on different databases.

bp4l-xp 12-24-2006 09:09 AM

is there any alternatives for mu wordpress and lyceum?


All times are GMT -7. The time now is 03:36 PM.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123