Steven S. Critchfield wrote:
----- "Howard" <[email protected]> wrote:
Am I making this more complicated than needed. I sure ain't making it
work!
Quick class on how debian/ubuntu are breaking down the apache configs
to try and make life nicer.
httpd.conf is the old way of doing everything here. So there should just
be an include to apache2.conf and the newer way of doing things.
apache2.conf should contain only the host generic configs, that that makes
apache stand up basically and get started.
mods-available/ contains the modules load and configs that are available for
your install. You can edit here, but it does not mean they are in use.
mods-enabled/ contains symlinks back to the mods-available/ and these are
in use. Remember that editing here edits in the mods-available/.
sites-available/ works like mods-available, create vhosts here to do any
site specific functionality.
sites-enabled/ symlinks back to sites-available. Sometimes you will prefix
the symlinks with numbers and such to ensure specific config read order.
Hopefully you have digested that.
Howard, for reverse proxy, I have dealt with that in the past by
building out virtual hosts. Set apache for namedvirtualhosts. Then build
a virtual host for each of the proxied machines and give it the information
needed for doing the reverse proxy such as where in the internal network
to proxy to.
Benefits are you configure only what you want to expose to the outside. You
can even put limitations easily enough on the proxy to limit access that
need to know external IPaddrs.
After looking at my install, make sure you linked to proxy_http.load,
proxy.load,
and proxy.conf in the mods-enabled.
<snip>
Many thank yous kind sirs. Greg and you have given me hope on my journey :)
"Set apache for namedvirtualhosts" implies a setting somewhere in
/etc/apache2.conf of which I am unaware (may already be set, I dunno).
Went Googling and have run into more of the abstract references that
don't get me past a bruised forehead.
Every reference I see lays out the <VirtualHost blah :80> ...
</VirtualHost> construct but neglects the token detail of ??Where??:
is this section added within /etc/apache2/sites-available/default
is this an additional section tacked on to the end of the above
how would these configurations result in there being
sites-enabled/000-default and sites-enabled/001-default (a detail of
curiosity not concern)
I'm lost in syntax to a large degree here.
Thank you for your example as it lays out the syntax within the
VirtualHost block. Now I need to know where to plug this block and with
which type of mortar.
Howard
--
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en
