Tidying up

[fivewood]

Now I have more than 1 site, I want to tidy up the way the files are stored on my hosting server so it doesnt get confusing

Currently I have all the files of 1 site in the public html folder (throwback to when I first started and only had the 1 site) with other sites in their own folders within that.

Kind of like this (if it helps to visualise)

Public Html Folder
--- Site 1 file
--- Site 1 file
--- Site 1 file
--- Site 1 file
--- Site 2 folder
------ Site 2 file
------ Site 2 file

Now what I want to do is move all of the site 1 files into their own folder, so it looks like this:

Public Html Folder
--- Site 1 folder
------ Site 1 file
------ Site 1 file
--- Site 2 folder
------ Site 2 file
------ Site 2 file

Much cleaner and less confusing
Moving the files is straightforward (I hope) but what do I need to do about redirects?
Obviously I want the URL for site 1 to remain the same, so I guess I need to do some sort of redirect

Any help gratefully appreciated

[scotserve]

Not quite as straightforward as it looks, you should not need redirects though unless you are using sub domains.
Stick a ticket in with details of domains etc and i will have a look and let you know whats involved.

[Rainee Bows]

I must admit that file structure still looks alien to me,

assuming sub-domains or add on domains ?

I may be revealing my fluffiness here ? but whats the reasoning behid using either to run trading sites ?

Is it just a case of not wanting to pay separate hosting charges ?? As i cant see any advantage myself for doing things that way (not meaning to be rude just not 'getting it' )


Rain
xxxx

[fivewood]

Not quite as straightforward as it looks, you should not need redirects though unless you are using sub domains.
Stick a ticket in with details of domains etc and i will have a look and let you know whats involved.

Thanks Bryon

I'll put in a ticket shortly

[fivewood]

I must admit that file structure still looks alien to me,

assuming sub-domains or add on domains ?

I may be revealing my fluffiness here ? but whats the reasoning behid using either to run trading sites ?

Is it just a case of not wanting to pay separate hosting charges ?? As i cant see any advantage myself for doing things that way (not meaning to be rude just not 'getting it' )


Rain
xxxx

Not getting round any charges as I already have a multi-site hosting account

It really is only a tidiness/safety thing
When I first started I only had the 1 site, so didnt think anything of having all the Prestashop files under the / directory.
When I add the 2nd start I gave it its own directory with all the files inside it.

What I have almost done a couple of times is edit a file in the / directory (the original site) instead of the 2nd site
Sorting the file locations now, would stop any chance of that happening and also makes the correct files easier to find (and looks a lot tidier!)

And when the rest of the sites get built....

[scotserve]

Just to help other people here

When you have a single domain on the account the structure is thus (Cpanel)
/home/accountname/public_html  Apache is told to look for the domain files in the /public_html directory this is called web root

When you have a multi account the control panel allows you to structer the web root so you can have /home/accountname/public_html as your primary site and /home/accountname/site2 as your second site etc etc however Fivewood has the following structure /home/accountname/public_html/site2 while this works it is not the preferred method
The primary domain should be left as is and the secondary site moved above /public_html this way there is less chance of making mistakes in terms of site structure, however since this is mapped into apache and Cpanel I need to look and see what is involved in moving this.

[JhnStcks]

Couldnt you just create ftp accounts for each site and give each ftp account access to the folders associated with the domain?

[Grifter]

Just to help other people here

When you have a single domain on the account the structure is thus (Cpanel)
/home/accountname/public_html  Apache is told to look for the domain files in the /public_html directory this is called web root

When you have a multi account the control panel allows you to structer the web root so you can have /home/accountname/public_html as your primary site and /home/accountname/site2 as your second site etc etc however Fivewood has the following structure /home/accountname/public_html/site2 while this works it is not the preferred method
The primary domain should be left as is and the secondary site moved above /public_html this way there is less chance of making mistakes in terms of site structure, however since this is mapped into apache and Cpanel I need to look and see what is involved in moving this.

Just looking at mine and they are the same. I thought that you had to do it like that because Cpanel autofills it /public_html/site2 for you. Have just changed one and now see what you mean. Just have to delete what cpanel puts in when creating the add on domain.

[Grifter]

Btw I renamed the folder public_html/site2 to tempsite2. Then went to add on domains. Deleted the domain. Then added it again without the public_html. Then copied the files and folders inside tempsite2 over to their right place.

[fivewood]

Lol Bryan - youve managed to completely confuse me now (not difficult I know!)

What do you mean by

the secondary site moved above /public_html

?

I'm quite happy to do this whichever way you suggest.
I was looking at it from a non techie point of view of tidiness and less mistakes


Presume when I create my next site I shouldnt be putting it in /home/accountname/public_html/site3 then 

[scotserve]

Lol Bryan - youve managed to completely confuse me now (not difficult I know!)

What do you mean by

the secondary site moved above /public_html

?

I'm quite happy to do this whichever way you suggest.
I was looking at it from a non techie point of view of tidiness and less mistakes


Presume when I create my next site I shouldnt be putting it in /home/accountname/public_html/site3 then 

Correct you should leave the path to / this will place any new sites in /home/accountname/new site

Grifters work around will work ok except if you have any email accounts on the site these  think will be removed when you delete the add on domain and re-create it

This will give you a structure thus
/home/accountname/public_html - this is for the primary domain on the account
/home/accountname/site2
/home/accountname/site3
/home/accountname/site4

if you do it the way you have site 2 could be seen as a directory of the primary domain - yes you could block access to this via robots.txt but only if they are compliant, the way i have outlined above avoids any issue with search engines as they cannot follow above the web root. It also keeps all site separate so little chance of editing the wrong files as all sites are within their own web root directory and can have separate ftp logins if you are paranoid.

I hope you dont mind me discussing this on forum rather than support ticket as it is an interesting topic that many may get a benefit from.

[fivewood]

I hope you dont mind me discussing this on forum rather than support ticket as it is an interesting topic that many may get a benefit from.

Not at all !

Think I'm beginning to understand what you are saying
The 2nd site isnt anywhere near being live yet, so how would I go around moving it to the structure you mention?
Is it just a case of moving the files?

[scotserve]

I hope you dont mind me discussing this on forum rather than support ticket as it is an interesting topic that many may get a benefit from.

Not at all !

Think I'm beginning to understand what you are saying
The 2nd site isnt anywhere near being live yet, so how would I go around moving it to the structure you mention?
Is it just a case of moving the files?

OK make a backup of site 2 or rename it to something else
Delete the add on domain and recreate it but with the / as location - now move your files from your backup or site2 directory into the newly created site2 directory - the database should remain intact but you will lose any email accounts you have created on this domain, all you need to do is change the path structures in your config files and everything should be OK ( assuming you are using zencart ) if Prestashop I think you can leave as is.

[Grifter]

my emails stayed intact.

[fivewood]

Thanks Bryon

Ive got limited internet access this week, so one for the weekend I think !