The apache guides are complete. They are basic installs with little to no configurations set except for what comes as default. For starters this ok but not if you plan to do more than host static pages. There is one more guide that needs to be written and that is to configure the server for SSL transaction. I am still working on that but priority on this feature is low. So the question is what now? I ask myself that too.

In one of the guides I make note the importance of documenting the PHP.INI file; any changes or updates applied are because many times, this is where the the source of the errors come from. The changes you apply to the HTTP.Conf, PHP.INI, or my.INI are dictated by the web application’s system requirements. The analogy I come up with is the web server is a "Gaming Computer" and the web applications are "High End Videogames". Some of the web apps will run fine on your server with no issues while other web apps have minimum requirements. Other times the web app requires something extra your web server may not support. That is where you make changes to your web server so it can support what the web app requires.

The guides are written so that Apache can be upgraded manually in pieces. There are self executables that will do this with one click, but upgrading Apache from the ground up gives you a better understanding how it all comes together. This also provides insight how to troubleshoot certain issues you come across. 

The next stop is looking at some open source applications and installing them on your test environment. Any updates or little things to make the application work will be noted for reference.