Like setting up a Firewall, foolproof nameservers and DNS, managing resellers, what are the priorities to lock down security and get right down to business.
Some of these are covered by the Webmin books (Jamie’s covers more topics and is much closer to comprehensive, mine is generally considered more beginner friendly but isn’t as deep or wide). Unfortunately, both books pre-date the existence Virtualmin by a couple of months, so they only cover the Webmin and Usermin aspects of the system.
A nice thing about using Virtualmin and Webmin is that a lot of these things are not specific to our way of doing things. So, if firewalls are of interest, the iptables HOWTO is an excellent resource that will map directly to your use of Webmin’s firewall module (which is completely compatible with doing everything from the command line as well). Our install.sh will be opening the ports generally needed for hosting in a not distant release, but it’ll never be able to guess what kinds of rules your system ought to have beyond that (and be very wary of any “this firewall script is all you’ll ever need” kind of things…they’re always way more complex than they need to be, since iptables is stateful, and they address a bunch of “problems” that haven’t been exploitable in the Linux kernel since the dawn of man…so they’ll distract you from the useful rules with a bunch of stupid and pointless rules).
I’m still beating my head against the wall that is OpenACS attempting to get to the point where I can safely upgrade Virtualmin.com to the latest version. The new version will give us access to a nice WYSIWYG wiki-like document editor, so we can begin to get our users involved in the process of documentation. Not necessarily writing it, though that would be awesome too, but just giving them the ability to comment directly on the contents of the documentation so we know where we’re being opaque, confusing, or covering the wrong things.
So far everything has been excellent.
That’s wonderful to hear. We’re trying very hard to make it the best thing going.
By the way - I’m not related to Joe :), that I know of at least…
Hehehe…My full name is Ronald Joseph Cooper. If my dad weren’t already a Ron Cooper, that would be the name I answered to. According to a PBS lookup from census data, Cooper is the 58th most common surname in the US, so we’re not exactly rare.
But I also don’t have any reason to believe we’re related, but I can’t rule it out. (I’m from upstate South Carolina stock, though I don’t know much of my family on the Cooper side.)
Is our license tied to an IP or server specific info?
No. It was made clear to us early on that customers didn’t like the way other virtual host administration tools were licensing crazy. You have to get permission to sneeze with those guys, and we didn’t want folks to feel like they have to get permission for everything they do. Our licensing is very unobtrusive. You get 30 days grace, where you can run your dev server and your production server on the same license and it won’t be flagged. Even after that, there are several circumstances where it won’t be flagged.
In short, as long as you’re trying to use it honestly, you should never be aware of the license management at all. If you ever do run into it, it’s probably a bug and we apologize in advance.