Configuration (Apache) - Revision history

Sstrutt: /* Status Page */ Added apachectl fullstatus

2012-07-24T06:54:32Z

Status Page: Added apachectl fullstatus

← Older revision		Revision as of 06:54, 24 July 2012
Line 63:		Line 63:
	</IfModule>		</IfModule>

	Restart Apache to apply (<code>~~service apache2 restart~~</code>), then access through through an URL similar to http://www.domain.com/server-status.		Restart Apache to apply (<code>apache2ctl -k graceful</code>), then access through through an URL similar to http://www.domain.com/server-status.

			If you also add <code>127.0.0.1</code> to the <code>Allow from</code> statement above you can get a status output to the console by using...
			* <code> apache2ctl fullstatus </code>

	For further info see http://httpd.apache.org/docs/2.2/mod/mod_status.html		For further info see http://httpd.apache.org/docs/2.2/mod/mod_status.html

	[[Category:Apache]]		[[Category:Apache]]

Sstrutt: /* User/pass restrictions */ Correction

2012-07-09T07:47:50Z

User/pass restrictions: Correction

← Older revision		Revision as of 07:47, 9 July 2012
Line 21:		Line 21:
	#* EG <code> /etc/apache2/sites-available/your-website </code> file, eg		#* EG <code> /etc/apache2/sites-available/your-website </code> file, eg
	# Restart the apache service		# Restart the apache service
	#* <code> ~~apachectl~~ -k graceful </code>		#* <code> apache2ctl -k graceful </code>

	<pre>		<pre>

Sstrutt: /* User/pass restrictions */ Re-orged

2012-07-09T07:44:43Z

User/pass restrictions: Re-orged

← Older revision		Revision as of 07:44, 9 July 2012
Line 15:		Line 15:

	== User/pass restrictions ==		== User/pass restrictions ==
			To restrict access to a site with a username and password
	# Create a user/pass entry in a file for a username		# Create a user/pass entry in a file for a username
	#* <code> htpasswd -c /~~usr/local~~/apache2~~/conf~~/htusers username </code>		#* <code> htpasswd -c /etc/apache2/htusers username </code>
	# Add the ~~relavent~~ bits to the ~~<code> /etc/apache2/httpd.conf </code>~~ file~~, eg~~		# Add the relevant bits to the config file for the website (see below)
	#* <code> ~~<Directory~~ /~~> </code>~~		#* EG <code> /etc/apache2/sites-available/your-website </code> file, eg
	~~#* <code> AuthType Basic </code>~~
	~~#* <code> AuthName "Restricted Access" </code>~~
	~~#* <code> AuthUserFile /usr/local~~/apache2/~~conf/htusers <~~/~~code>~~
	~~#* <code> Require valid~~-~~user </code>~~
	~~#* <code> </Directory>~~ </code>
	# Restart the apache service		# Restart the apache service
	#* <code> ~~service~~ apache2 ~~restart~~ </~~code~~>		#* <code> apachectl -k graceful </code>

			<pre>
			<Directory />
			AuthType Basic
			AuthName "Restricted Access"
			AuthUserFile /etc/apache2/htusers
			Require valid-user
			</Directory>
			</pre>

			See also [[Secure Website]]

	== Status Page ==		== Status Page ==

Sstrutt: Added "Status Page"

2012-03-15T12:26:12Z

Added "Status Page"

@@ Line 26: / Line 26: @@
 # Restart the apache service
 #* <code> service apache2 restart </code>
 [[Category:Apache]]

Sstrutt: Initial creation - content from Apache page

2012-02-09T10:46:21Z

Initial creation - content from Apache page

New page

== Log Rotation ==
There are two ways to ensure your logs get rotated...
* logrotate - The standard, cross application log rotation solution. Its very reliable and easy to configure, but requires that Apache is restarted every time your log is rotated so that it follows the log switch around.
* rotatelog pipe - Has more overhead as logs are piped to a child process to handle, but doesn't require Apache restarts.

=== rotatelog ===
Edit you existing config file to redirect logging through the child rotatelogs process, this will probably be found in either your site config (EG in <code>/etc/apache2/sites-enabled</code>) or your Apache service config (EG in <code> /etc/apache2/ </code>)

ErrorLog "|/usr/sbin/rotatelogs /var/log/apache2/error-%Y-%m-%d.log 86400"
CustomLog "|/usr/sbin/rotatelogs /var/log/apache2/access-%Y-%m-%d.log 86400" combined

Check that the path for <code>rotatelogs</code> is correct (search using <code> find / -iname rotatelogs </code>)

Restart Apache, perform a test page load on your site (that would generate log entries), and check that a log file has been generated as per your config

== User/pass restrictions ==
# Create a user/pass entry in a file for a username
#* <code> htpasswd -c /usr/local/apache2/conf/htusers username </code>
# Add the relavent bits to the <code> /etc/apache2/httpd.conf </code> file, eg
#* <code> <Directory /> </code>
#* <code> AuthType Basic </code>
#* <code> AuthName "Restricted Access" </code>
#* <code> AuthUserFile /usr/local/apache2/conf/htusers </code>
#* <code> Require valid-user </code>
#* <code> </Directory> </code>
# Restart the apache service
#* <code> service apache2 restart </code>

[[Category:Apache]]