I understand why you might use the AMPP product on windows, a
development machine is hard to get working on it.

With the DEB files it is easy on Ubuntu. So Don't understand accepting
the limitations imposed with AMPP.

Symlinks are easy! /var/www/ is a root owned directory requiring super
user permission, that makes it safe, that is also why the SQL
administering program is not there and should be accessed via symlink.

I gave up Windows because of security issues, so I don't want to do
things that vary from conventions. I prefer development of Linux that
refuses to open holes to make it easer to use.

You have 3 options:
1. use lampp use the apache manual to secure apache and the other
servers you are installing so your install can't be hacked.

2. Use chown to change permissions of your ./www directory while you
insert the stuff you will be using then change back the permissions.

3. set-up a user folder and insert a symlink to your stuff into the
./www folder.

For the outside world looking in the symlink seems to me more secure,
I may be wrong but without a path to follow, changes would be tuff,
most likely why the developers make you do some of the work.

I am new to the Linux community(4 mos), and have gone to the
developers forums to understand how to make my system do what I
thought should be easy. I have noticed that when things are hard to
do, the developers made a security decision. With Windows the decision
is ease, and for Linux security. How many bugs do you have in your
house? Accept that a bug free house requires work, don't open your
system to issues that brought you here.

To make a symlink use ln -s (/from) (/to). Details can be found in
the Linux command manuals on line. You may need to change users to do
all of this, I know you will in the root directory.

If you want to be able to mess with your web files make the sym link
point to your user directory i.e. /user/username/webfiles/ Then you as
username can put your pages in without the terminal, a big plus!