Skip to main content
O
osgood_
Legend
March 29, 2017
Answered

3 websites, 1 server?

  • March 29, 2017
  • 2 replies
  • 793 views

This is probably ok but I've personally never come across this kind of set-up before. Any downsides or opinions?

I have a client with 3 websites and they want me to upgrade just the 1 website.

When I sign into the ftp area I see 3 different websites in 3 different Folders - folder_name_A, folder_name_B, folder_name_C. No 'public' or 'html' folders etc

So when you type into the browser www.folder_name_A.co.uk you get taken to that companies website and www.folder_name_B etc, you get taken to that companies wesbite.

Its not ideal if you're writting some bespoke CMS as it leaves it wide open to copying by other developers who have access to work on site_B and site_C

Not that much of an issue for me as my CMS is fairly standard which anyone who has a moderate knowledge of php can produce so its hardly likely to be copied or if it is no-ones going to make money out of it.

I'm more interested if its a good set up or a bad one. I dont particularly like it myself.

Cheers

Os

    This topic has been closed for replies.
    Correct answer Rob Hecker2

    I have 15 websites on one web server (as in one cPanel account). They all use the same database, but it's possible to have a number of databases also.

    I'm sure some shared hosting plans limit what you can do, but if the plan allows it, no problem.

    Since each website is in its own folder, there probably won't even be a need to edit the htaccess file.

    it leaves it wide open to copying by other developers

    this is why the server belongs to me; not the clients. Not even my mama has access to my server files.

    Actually, multiple sites on a single web server is not the problem. Allowing other coders to access the account is the problem. They can f*k something up without your knowledge and then who has to resolve the issue? Then the finger pointing begins.

    2 replies

    pziecina
    pziecina
    Legend
    March 29, 2017

    The only times i have seen such a configuration, is when one person is managing all the sites hosted.

    It may be worth asking why they are doing it that way.

    Rob Hecker2
    Rob Hecker2
    Legend
    March 29, 2017

    With a cloud vps, like AWS, they can have one account with one set of resources (bandwidth, cpu, storage) but they can have multiple "droplet" that are basically separate little server instances. Each can even have a different OS (I think). That might be a way to keep the other developers out of your turf.

    In the US, Linode is a good cloud VPS provider. In the UK I don't know.

    pziecina
    pziecina
    Legend
    March 29, 2017

    I know this is going to annoy a few people Rob, but I have found the Microsoft Cloud services to be one of the best, even from the U/K.

    Rob Hecker2
    Rob Hecker2Correct answer
    Legend
    March 29, 2017

    I have 15 websites on one web server (as in one cPanel account). They all use the same database, but it's possible to have a number of databases also.

    I'm sure some shared hosting plans limit what you can do, but if the plan allows it, no problem.

    Since each website is in its own folder, there probably won't even be a need to edit the htaccess file.

    it leaves it wide open to copying by other developers

    this is why the server belongs to me; not the clients. Not even my mama has access to my server files.

    Actually, multiple sites on a single web server is not the problem. Allowing other coders to access the account is the problem. They can f*k something up without your knowledge and then who has to resolve the issue? Then the finger pointing begins.

    O
    osgood_Author
    Legend
    March 29, 2017

    https://forums.adobe.com/people/Rob+Hecker2  wrote

    Actually, multiple sites on a single web server is not the problem. Allowing other coders to access the account is the problem. They can f*k something up without your knowledge and then who has to resolve the issue? Then the finger pointing begins.

    Yes, that was my biggest concern but hey-ho not sure I can do much about it. Take the money and run. I don't get much business once a CMS is deployed so if it works when I hand it off and later it stops working should I really care, it's not really under my management.

    I had a recent example of this just the other day. The hosting company upgraded the server with something without informing anyone and the site stopped working and no it wasn't php 7 (this site is 4 years old and used the DW server behaviours in some sections). They denied all and blamed someone else for poking around in the cPanel changing database permissions. I discovered a bit of simple php code, totally unrelated to database permissions, that had worked for 4 years had stopped working, that doesnt happen unless the server set up changes in some way. Of course everyone denied responsibility. Thankfully it was simple to put the code right but yes it did fall on my shoulders, everyone else involved f•k up and walked away, as I usually find they do these days.

    Ok so not really a problem apart from could be a bit open to 'abuse'.

    Thanks Rob.

    Os

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices