ISPConfig is quite a good basic tutorial, but it only does exactly what it does; it doesn’t really explain much, just gives you a ‘do this, then do that’ walk through the steps.
Now, if you know not much, don’t want to know anything, and want exactly the ISP Configuration, that’s fine. The trouble is, if you want something different, even slightly different, you probably don’t have much that you can do about it. You would, if it explained everything, but it doesn’t.
from there, you seem to have a few options:
- give up
- follow a different tutorial, one that explains stuff
- work out what you really want and how to fix ISPConfig to get it and do that
- work it all out for yourself
- put up with what it does
The 32/64 bit issue makes no difference to the principles, but it may make a difference to filenames, in places. From 10,000 feet, the only difference is that 64 bit allows support of more memory (I know this is an oversimplification, but…) and you can do it either way. If you are only able to exactly follow a tutorial, you’ll probably have to do exactly what the tutorial does.
After fruitless searches, I come here. Hoping someone can point me to a nice walkthrough on initial installation
that part is easy-ish, you could even follow the first part of the ISPConfig tutorial. I happen to like the Linuxhomenetworking tut linked earlier, so that’s what I’d have suggested you look at, too. If you can explain which parts of that you get stuck at…
and then setting up a web server and mail server.
Web server:
you could just install Apache, you could follow the web server part of the ISPConfig tut, or you could wander over to Bitnami and install one of their stacks that includes a webserver…if, eventually you want something like wordpress or a CMS, this approach has something to recommend it.
You’ll have to ask someone else about the mailserver bit.
I do have static IP addresses ( leasing a block from ISP ) and a domain name.
OK, this brings a new fact (probably); everything that have written up to that point was consistent with this being a server for use on your internal network only.
If this is also for external use, security becomes a big issue. Don’t do this unless you understand the issues and can find your way around a firewall. (There are certainly other bits of security too - I wouldn’t like you to think a firewall is the end of the story, but it is an absolute minimum requirement).
