You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Question: apache and ftp config best practise?:

#3 Re: Question: apache and ftp config best practise? Posted by matej (158.193.xx.xx) on Fri 30 Sep 2005 at 16:50 it depends on many factors. most important factor is number of users & virtual hosts you are going to host, as well as other small questions - from "what about mail hosting" to "one ftp user = one site, or unlimited, or.." and similar. "by hand" is most flexible configuration system I ever used. by flexibility I mean that you can configure every account to your wish, enable/disable services, add vhosts to one account, setup quotas or aliases any way you want. you can put home dirs wherever you wish, docroots as well, use symlinks or don't. there're so many options, each with its own set of pros and cons that I cannot enumerate them. however, this system is hard to manage once number of users reaches 50 or 100 (if you write handful of scripts you can make it even over these numbers, sure). (very) small providers, say <5k users, should either pretty fine tune their scripts inhouse, or try to find some isp-support software. there are some on sf.net, freshmeat.net, ... (well, sf has 9 project in alpha planing state to 1 usable, I know). if you decide to go with some similar product, follow his rules. you'll save troubles later. larger providers cannot live without such system.

Username:	Anonymous
Title:
Your Comment:
Posting Format:	BBCode HTML Text Plain Text Textile

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account