>> I currently have a VPS running @ vpsland.com running all of the above.
>>
>> It would help to focus on saving memory. For example, lighttpd
>> (http://en.wikipedia.org/wiki/Lighttpd) instead of Apache. I used it
>> currently to run squirrelmail which is php based webmail. Works fast
>> and flawlessly.
>>
>> You will also want to set up amavisd-new and clamav for spam\virus
>> filtering for postfix.
>>
>> I find these perfect setup guides as they are very intuitive.
>> Here is one for Debian Etch (which I see is what johncompanies is
>> offering)
>>
>> http://www.howtoforge.com/perfect_setup_debian_etch?s=04090aedb4a47b9ba3407539be6ad4e5&
>>
>
> Good reference, though it's pretty light on *why* you do these things.
> On the other hand, it mentions ISPConfig, which I hadn't thought about.
> This came up on the list at one time and someone who runs a hosting
> service (Rich Morgan?) didn't think much of it. I didn't need it at the
> time, so I didn't think much about it after that. But it sure would make
> things easier.
You are correct, it is not a very comprehensive guide. They also leave
out spam and virus filtering, which IMO is a necessity.
>
> On the other hand, a control panel like ISPConfig would obviate some of
> the stuff I need to learn, since it would do a lot of those things for me.
>
> I've looked at some of the docs for ISPConfig. I understand why Debian
> doesn't offer it. It wants to install on a "new" system, and insists on
> recompiling Apache, among other things. It also wants some things in
> places where Debian doesn't put them.
>
> Still, for an ongoing solution, it sounds good. The idea of having to
> tweak postfix and apache by hand every time I had a user or website
> would be a pain. I was figuring I'd have to write scripts to
> semi-automate the processes.
>
> There's also a possibility I can get this on Linux.com, instead of
> hosting it on some site of mine. In which case, I'll have to go through
> the whole process of learning all the packages, just to complete the
> evolution.
>
> Here's an idea: What if I installed ISPConfig, configured everything
> using that, and then used the resultant config files for the various
> packages as examples in learning how to manually configure them?
> (Starting from scratch on each one of these is a bear.)
>
> Paul
I have never installed it but the tutorial above says it works out of
the box?
To me ISPConfig is overkill for what I have running. I use webmin for
remote gui stuff. You could learn how to manually configure your
services via the ISPConfig config files. Personally it would be too much
to stuff in my head at once. I like learning one daemon at a time. :)
Have you started a straw-man on your system design?
Some things I had to think about.
Bind: caching only or Authoritative for my domain?
I picked caching only and used my providers DNS servers as DNS
forwarders. My reason for this is because I have a grandfathered free
account at dyndns.org. They have redundant DNS servers which manage my
domain. If I ran authoritative then I would only have 1 server and it
would be attached to my VPS IP address. With my dyndns.org account
everything remains portable IP address wise. It is also free for me
where otherwise you would have to pay $24/year.
Web server: Apache or lighttpd.
I only have 128m/256swap on my vps. Comparatively Apache is
a pig compared to lighttpd. For my needs lighttpd is perfect. Apache
wins in the flexibility dept though.
mail: Postfix. No brainer. With SMTP-AUTH and TLS
spam/virus: amavisd-new and clamav. Sing together in harmony. Seems the
most popular and well documented setup. It is a memory hog though. The
largest on my system.
IMAP: Dovecot over SSL. This is how I get my mail.
-Chris
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:56:09 EDT