Switching from Hatchling to Baby (shared)

[michiel]

Hi,

I have one hatchling account at HG and have a different website hosted at one.com. I'm considering upgrading my hatchling account to a baby account since the baby account allows more than one domain to be linked to the account.

I would like to know if both domains will be separated on my account. And with 'separated' I mean; the ability to have two different storage-spaces within my account with both a different public_html folder and the ability to create a second mysql db. Both websites cannot simply be dumped into the same folder and I'm worried that the baby account upgrade is simply an upgrade in bandwith and weight, without having the ability to split my websites.

thx for the help!

michiel

[eLIANT]

Originally Posted by michiel

...the ability to have two different storage-spaces within my account with both a different public_html folder and the ability to create a second mysql db. Both websites cannot simply be dumped into the same folder and I'm worried that the baby account upgrade is simply an upgrade in bandwith and weight, without having the ability to split my websites.

Read up on "Add-on Domains."

Here's how it works:
- primary domain HTML & associated files go in public_html
- Add-on domain HTML & associated files go in public_html/AddOnDirName
- there is ONLY 1 cPanel which you will use to manage primary and Add-on Domains (Add-ons do not get their own CP.)
- however many DBs you create for primary or for Add-on, they are all managed from within that one CP; open phpMyAdmin and it will ask you which DB you want to Administer from a list of all DBs from ALL domains (primary and Add-on.)
- ALL emaill address for ALL domains managed from 1 CP
.
.
.
- etc

If you are the web admin for multiple sites, this is a pretty straightforward management method. However, if someone else (a customer of yours) is going to manage their own site, you'll need to move to a reseller package so they can have THEIR OWN CP.

[michiel]

So if I would register two domains, domaina.com being my primary domain, domainb.com would;

- have a CPanel located at domaina.com/cpanel;
- have a mailserver located at domaina.com/webmail;
- have a public_html located at domainb.com/public_html

and www.domainb.com would request /domainb.com/public_html/index.html ?

thx for the support

[eLIANT]

Originally Posted by michiel

So if I would register two domains, domaina.com being my primary domain, domainb.com would;

- have a CPanel located at domaina.com/cpanel;

Sort of. Remember, there is only 1 CP, and even though you can access it via domaina.com/cpanel or domainb.com/cpanel, it's still the same CP (and you'll use the same username and password no matter which domainX.com/cpanel you put in your browser.) So your stetment, "domainb.com would have a CPanel located at domaina.com/cpanel" is not completely accurate. ALL aspects of managing ALL domains (both a and b, and any others in the future) will be done via that one cPanel.

Originally Posted by michiel

domainb.com would have a mailserver located at domaina.com/webmail

Yes, they can access their mail that way; however, you will probably advise your domainb clients to access their mail via domainB.com since this will make more sense to them.

Originally Posted by michiel

have a public_html located at domainb.com/public_html

No. The file structure for the 2 domains looks like this:
DOMAINA
/root/public_html/domainA files

DOMAINB
/root/public_html/domainBdirectoryNameYouMadeUp/domainB files