-------------------------------------
This is the WAeUP nginx configuration
-------------------------------------

Installation
------------

1: Put the files in this directory into /etc/nginx and copy
   `nginx-init` to::

	/etc/init.d/nginx

   This is the start script to start/stop/restart nginx.

2: To make nginx startup properly, you must provide a file `nginx` in
   /etc/default/, that at least contains the line::

	startup=1

   Otherwise nginx will complain and refuse to start.



Running nginx
-------------

Currently, two portals are served by the configuration: fceokene and
uniben. Both portals can be started in maintenance mode by using the
-muniben and -mfceokene option respectively::

	# /etc/init.d/nginx -muniben restart

will start the uniben portal in maintenance mode while fceokene will
be started in production mode. ::

	# /etc/init.d/nginx -muniben -mfceokene restart

will put both portals into maintenance mode, while ::

	# /etc/init.d/nginx restart

will start both portals in regular mode.



Configuration
-------------

In directory `general/` you can find the more general settings like
proxy settings, base values etc.

`charmaps/` contains some character maps, which are currently not used.

`sites` contains the virtual host specific configurations for uniben,
fceokene etc.


Static Resources
****************

Using static resources (i.e.: images, documents, etc.) speeds up
things a lot.

Currently, static resources can be placed in

	   /zope/instances/srp-static/uniben/static/

for the uniben portal and into

	   /zope/instances/srp-static/fceokene/static/

for the fceokene portal. They are accessible via URL when the path of
the URL starts with `/static/`. Using such URL bypasses Zope.

Example::

	Put a file mypic.jpg into
	/zope/instances/srp-static/uniben/static/ and call 

        https://uniben.waeup.org/static/mypic.jpg

        with your webbrowser afterwards.

        The image will not be served by Zope but instead be delivered
	by nginx immediately, bypassing Zope.

Note: to make nginx determine the correct content type for your
resources, your files have to provide a well-known filename extension
(as: .txt, .jpg, .doc, etc.). If your file is named 'myfile', it will
be served as plain text (not: html).