[Bug 239048] Re: apache2 conf.d and sites-enabled oops

[tgpae]

Update: Checking my config history, this was not introduced when I
thought it was.  I merely hadn't restarted apache after putting
everything in version control.

The base principle still applies: one should not have the default
configuration preclude revision control.  Checking on things further,
Subversion (svn) also puts a subdirectory in each managed directory.

** Description changed:

  Binary package hint: apache2.2-common
  
  In the latest apache2 default config files, the last lines are
  
  # Include generic snippets of statements
  Include /etc/apache2/conf.d/
  
  # Include the virtual host configurations:
  Include /etc/apache2/sites-enabled/
  
  Any serious web server has its files under version control.  I believe
  many version control packages add additional files to the directory; at
  least CVS, RCS, and SCCS do - CVS adds a CVS directory, with a few
  special files to point back to the repository, and the other two
  actually store all of the repositories within a subdirectory.  The two
  include lines above will attempt to load all of these revision-control
  related files as apache config files, which will not work.
  
  
  I've kludged this for my system with the following, which has me back up and running:
  
  # Include generic snippets of statements
  Include /etc/apache2/conf.d/[a-z]*
  
  # Include the virtual host configurations:
  Include /etc/apache2/sites-enabled/*-*
  
  
- This problem is in apache2-common 2.2.8-1ubuntu0.2; it was not in apache2-common 2.2.8-1ubuntu0.1.
+ This problem is in apache2-common 2.2.8-1ubuntu0.2.
+ Edit: it was also in apache2-common 2.2.8-1ubuntu0.1.

-- 
apache2 conf.d and sites-enabled oops
https://bugs.launchpad.net/bugs/239048
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.