XAMPP, Part 3
In dealing with security, there are some essential concepts that we all need to wrestle with. On the one side, we want to share our stuff, or at least certain parts of it. On the other side, we need to keep safe and private the things we don’t want others to know about, steal or damage and destroy.
Perhaps you want to just open your WAMP up to the rest of the machines in your local network. But if we’re going to open it up to a larger audience, we had best know how to set up the fences and close the open doors. This article will describe the basic ways we have of securing XAMPP for Windows.
A few words of caution before you do that: Be prudent, and don’t disrupt other people’s operations. If it’s your own network (not your employer’s), you’re free to do whatever you want. However, opening the gate to the Internet requires some serious study of the consequences. There are LOTS of malicious people who would love to put key loggers or Trojans on all the systems connected to your LAN. DON’T make it easy for them.
In order to make this a bit more useful, I started all the XAMPP programs, including Mercury Mail and FileZilla Server, and then opened http://localhost/xampp to get the XAMPP Status Screen.
XAMPP, Part 2
Now that you have a basic XAMPP for Windows system installed and running, what’s next? Let’s first look at the XAMPP Status link. (You can click on the picture to enlarge it, and use your browser’s “back” button to return here.)
Let’s recap what is currently working according to this chart. Continue reading
XAMPP, Part 1
The first WAMP stack I’m reviewing is XAMPP. Because it is a popular package, I thought there should be a lot of information already available about it, and the obvious first place to look is the ApacheFriends website. While their offerings are available in several other languages, I’m going to stick to English for this series. 😉 I found out, however, that the information can be a bit sparse, so I Googled it and found a few other (somewhat) helpful pages. I think you’ll find this one both up-to-date and generally more useful (IMHO).
I have been using XAMPP for Windows for about five years and it has proven to be an effective and well-maintained package. It’s an easy package to install and can also be set up as a portable environment, like on a USB memory stick. It has several included subsystems that help make it a good package to perform tests.
Over the past few years, I’d get a package that was supposed to help me create a Website for Internet marketing. “Just add it to your hosting service and you’re ready to go!” Well, not quite. How does one go about preparing, configuring, testing, and deploying such a package? There are many more things to do to get it functional. When you start, it’s almost overwhelming.
Writing an HTML file and displaying it in your browser is so far away from running an online Website, that it defies comparison. As a next step, you can get a regular shared host service, but that implies that you know what you want to do (to some extent). It may make you feel a bit queasy, since all your experimentation and partial pages are on the Web for whomever to see. If you’re just trying to get your arms around it all first, you may feel like you’re jumping onto a moving train. Continue reading