Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Sun May 29, 2011 5:40 pm 
Offline
Newbie

Joined: Sat May 21, 2011 7:12 am
Posts: 3
Website: http://www.designfuture.it
WLM: stermi@gmail.com
Location: Lucca
Hi all, I'm going to buy a linode vps and I want to use it for many purpose:

- redmine + svn/git for project managing and repositories
- a groupware server ( egroupware / zimbra / something else )
- many site hosting

So I have my main website with /var/svn and /var/git for repository and I'm a bit confused on how to structure it for websites.

I usually have only 1 localhost webserver and I have only 1 website on it. So before starting configuring my vps I want to ask you: which is the best way to organize my server?

I have 5 sites (example) to handle.
Have I to create 5 apache configuration ( site-enabled ) that point to 5 different home locations?

- /home/project1/public_html/
- /home/project2/public_html/
- so on....

Is this the best way? How do you do?
Sorry for the stupid question but I want to make my server very clean on the structure :)


Top
   
 Post subject:
PostPosted: Sun May 29, 2011 9:36 pm 
Offline
Senior Member

Joined: Wed May 13, 2009 1:18 am
Posts: 681
I think the answer that there is no right answer, so if you can come up with a structure that is manageable and makes sense to you, it's fine :-)

With that said, for my own systems, I've taken to using the /srv tree for most of my major hierarchies. You can use the top level as a service divider (e.g., /srv/svn, /srv/www) and the next level for per-machine/user/host, or invert the order, which is typically what I do (so /srv/xxxx/{svn,www,db,...} where xxxx is a company or common category for all the functions. Or combine the two approaches...

I also try to ensure uniqueness of the naming of the tree for any given purpose, so that when looking at multiple systems, I could theoretically combine all of their /srv trees safely if I wanted. Or taken another way, regardless of machine, a given /srv/xxx tree always has the same purpose.

I normally go ahead and make /srv (or for larger setups, each /srv/xxx) its own disk image for my Linode.

-- David


Top
   
 Post subject:
PostPosted: Mon May 30, 2011 5:51 am 
Offline
Senior Member

Joined: Sun Mar 07, 2010 7:47 pm
Posts: 1970
Website: http://www.rwky.net
Location: Earth
I go for the /home route, i.e.
/home/user/public_html
/home/user1/public_html
etc etc.
Then I have /home/git/user and /home/git/user1 to hold the git repos.

No real reason for it, probably because I started off with shared hosting on cpanel years ago which always sticks you in /home/user/public_html

Some of my clients have stuff in /srv and that works too.

Just pick something that you feel most comfortable with and stick to it.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group