----- "Howard" <[email protected]> wrote: > 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.
The example I pulled was a file I called /etc/apache2/sites-available/home_forward I didn't care about the order of config loading, so I didn't bother to link it as anything other than that when I put it in the sites-enabled. The name of the file doesn't mean anything at all. The mortar you are looking to see is at the end of the apache2.conf file that is # Include the virtual host configurations: Include /etc/apache2/sites-enabled/ As it ends in a /, apache knows that to be a directory and includes everything inside of it. Further pointing to the mortar, all these separate files are only separate for our administrative purposes. You will find they all end up being included at some point into the original httpd.conf. httpd.conf includes apache2.conf apache2.conf includes all the mods-enabled load files apache2.conf includes all the mods-enabled conf files apache2.conf includes the ports.conf file apache2.conf includes all the files sitting down conf.d/ Think of it as a great way to experiment. You could create a file with some edits you found, toss it in the conf.d dir and restart apache to see it work. If it blows up, or doesn't work the way you like, you go pull the file and you are back to your original config. BTW, I just grepped over my configs, guess I am not using namedvirtualhost in my configs either. So ignore that suggestion. -- Steven Critchfield [email protected] -- 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
