Member sites on 1 server or multiple servers?

[McFly85]

I have one member site using CCBill and plan to create a couple more member sites. I'd like them all to share the same .htpasswd database so they can access all sites. I was told by CCBill the only way for this to work was to put all sites on one server. Is this a smart thing to do or should I put my sites on separate servers?

I guess if I put them on separate servers I'll need a new user management system so members of each site can access all the other sites. Any suggestions what I can get to allow that?

[JuiceMonkey]

There are actually a ton more options.. (load balancing, clustering, virtualization), hit me up if you need some help.

[CaroMark]

There are actually a ton more options.. (load balancing, clustering, virtualization), hit me up if you need some help.

Good recommendations from JuiceMonkey! Make sure that as you consider growth as you putting your plan into place.

[directfiesta]

There are actually a ton more options.. (load balancing, clustering, virtualization), hit me up if you need some help.

that is right.

Or he could use rsync in a cron job to sync the password file between servers.

[raymor]

I'd just use a mysql database. We have a replacement CCBill script which
will write to MySQL instead of a file and I think they have their own
version now too. You can then use Strongbox to read that MySQL database
and of course at the same time protect you from password traders,
brute force attacks, etc.

[raymor]

Oh I forgot to say -
While you CAN get into a lot of esoteric configurations with load balancing,
clustering, rsync, etc. all have significant complexities and will create new
problems that you'd have to solve. I'd hghly suggest going with the simplest
solution unless you have an overriding need to do something complex.

[Hell House Vic]

i think raymor's answer is the best.

but for simplicity sake, there is no real problem putting more than one site on a server, until you start to overload that server. So I would first go the simple route and make the best use of one server. and WHEN YOU NEED TO , expand to multiple servers and use raymor's solution.

[SkeetSkeet]

Strongbox can set that up for you as well

[brandonstills]

You can have the site go through a database as mentioned above. Not sure if CCBill has a script for your server that does that. It may require some custom work.

Another option is to set up some kind of cron job to copy the .htpasswd file every few minutes or so.

[tom3k]

whatever you decide to do, do it as early as possible.

doing 'change overs' will cost you extra time (and ultimately money).