dean1012
08-06-2007, 03:29 PM
I wasn't sure of a better title so excuse me if I chose the wrong title for this thread.
As I will be opening a shared hosting business soon (*just* shared web hosting), I have been thinking of a lot of different things lately. One of them is the separation of the business site/support system and customer sites.
I have a dedicated server that I definitely plan to put my customer sites on. I could also place my business site and support/billing system on it as well.
The problem there, obviously, is that if my server gets knocked off the web, my business website goes down as well and with it goes the support system.
Customers aren't going to be happy if they see their site down and run to my support system to realize they can't contact me!
I will be using a PHP/MySQL site as my business website and WHMCS as my billing/support system.
If I move my business site and billing/support system to an external area (in a different datacenter even), if my server(s) go down customers can still maintain full contact with me. This means e-mail, support ticket, live chat, and any other support mechanism I choose to offer will work. In addition, I will have the main site up to post an announcement about the downtime.
Obviously, if at all possible, I should separate my business site and billing/support system from my customers' sites.
So, I have a few questions about it. Please only reply if you have specific experience with WHMCS and it's requirements (HDD, Bandwidth, CPU/RAM, Prereq. Software, etc...).
1) What kind of hosting account could run it? Shared? VPS?
2) Is it safe/secure to run WHMCS in a shared environment? What about VPS?
3) When looking for a shared/VPS provider, is there any particular special software I should look for? (Particularly any software required by WHMCS)
4) What about automatic billing, suspension, etc... Is this supported during this separation? IE, can I have WHMCS know the details for my dedicated server and automatically suspend those accounts if payment is not made? This would imply that the automatic billing would be handled on the shared/VPS provider's side.
5) What kind of specs should I look for in a shared provider for this solution? What about VPS? I already have nameservers, dns, etc... I'd be looking for 1 dedicated IP to support my SSL, though.
6) Can you recommend any specific shared/VPS providers for this matter? Reliability and uptime is the most important thing. If I am taking my business site and billing/support system off of my dedicated server, I'm exchanging some control over the situation for the hopes of my site being online no matter what problems arise.
7) Is there a better solution than separation? The goal is to make sure customers can access my site and billing/support system even during the toughest of downtimes. It should take a widespread disaster (or a huge stroke of bad luck) to knock both customer sites and the business site down along with the billing/support system.
Thank you,
Jerry Smith
As I will be opening a shared hosting business soon (*just* shared web hosting), I have been thinking of a lot of different things lately. One of them is the separation of the business site/support system and customer sites.
I have a dedicated server that I definitely plan to put my customer sites on. I could also place my business site and support/billing system on it as well.
The problem there, obviously, is that if my server gets knocked off the web, my business website goes down as well and with it goes the support system.
Customers aren't going to be happy if they see their site down and run to my support system to realize they can't contact me!
I will be using a PHP/MySQL site as my business website and WHMCS as my billing/support system.
If I move my business site and billing/support system to an external area (in a different datacenter even), if my server(s) go down customers can still maintain full contact with me. This means e-mail, support ticket, live chat, and any other support mechanism I choose to offer will work. In addition, I will have the main site up to post an announcement about the downtime.
Obviously, if at all possible, I should separate my business site and billing/support system from my customers' sites.
So, I have a few questions about it. Please only reply if you have specific experience with WHMCS and it's requirements (HDD, Bandwidth, CPU/RAM, Prereq. Software, etc...).
1) What kind of hosting account could run it? Shared? VPS?
2) Is it safe/secure to run WHMCS in a shared environment? What about VPS?
3) When looking for a shared/VPS provider, is there any particular special software I should look for? (Particularly any software required by WHMCS)
4) What about automatic billing, suspension, etc... Is this supported during this separation? IE, can I have WHMCS know the details for my dedicated server and automatically suspend those accounts if payment is not made? This would imply that the automatic billing would be handled on the shared/VPS provider's side.
5) What kind of specs should I look for in a shared provider for this solution? What about VPS? I already have nameservers, dns, etc... I'd be looking for 1 dedicated IP to support my SSL, though.
6) Can you recommend any specific shared/VPS providers for this matter? Reliability and uptime is the most important thing. If I am taking my business site and billing/support system off of my dedicated server, I'm exchanging some control over the situation for the hopes of my site being online no matter what problems arise.
7) Is there a better solution than separation? The goal is to make sure customers can access my site and billing/support system even during the toughest of downtimes. It should take a widespread disaster (or a huge stroke of bad luck) to knock both customer sites and the business site down along with the billing/support system.
Thank you,
Jerry Smith
