This configuration example shows a few of the newly developed advanced 
options. We use it at our institute as a visitor registration database. 
Before someone from our collaboration visits the institute, she/he has to 
register on this public logbook.

Following advanced functionality is used:

- The arrival and departure dates are attributes of type "date". This way 
a visitor can select the date from the date picker. In addition, the 
entries can be sorted according to the arrival date. Using a quick filter 
on arrival date, one can show the new arrivals for the next week, next 
month and so on. By adding a bookmark to the browser in the form

http://server.domain/Visitor%20Registration/?Arrival+date=7

one can click on that bookmark to see who will come in the upcoming week. 
Using the find page, one can query the database for arbitrary arrival and 
departure dates, like "who was here last year between May and July?".

- The "visitor" and "email" attributes are preset with the name and email 
of the current user. Of course every user has to register on that logbook 
(enabled with "self register = 2")

- The attribute "Home Institute" can be chosen from a list of preset 
institutes. Using the home institute as a conditional attribute, the elogd 
server fills in automatically the fax number of the institute (see the 
list {1},{2}, ...) after it has been selected.

- Email notifications are set up such that on each new registration, an 
email is sent to stefan.ritt@psi.ch, and an email is sent to 
radiation@psi.ch if the check box "Radiation badge" is checked. Please 
change the smtp server host name to make email notifications work.

elog:/1 shows an example entry screen.

Welcome to the "Config Examples" logbook. This database contains elogd.cfg 
examples from various users, showing how ELOG can be configured for various 
purposes. Feel free to use these configuration files as a starting point 
for your own logbook.

To enter a new configuration example, you have to register an account on 
the "Forum" logbook, then you can log in with the same username and 
password to this database.

Then you are supposed to upload your "elogd.cfg", but I suggest to first 
rename it locally to "elogd.txt" and then upload it. This way it gets 
automatically displayed below the message body, so people can see the 
message body and the contents of the configuration file at the same time.

If you want to revise your entry at a later time, hit 'edit', delete your 
old attachment, and submit your new 'elogd.txt' file.

sample of standard elog css and class name
http://public.mba.be/demo/elog/elog_test_css.htm

This will let you use <site>/elog/ as your URL.

    location /elog/ {
        proxy_pass http://127.0.0.1:8080/;
        proxy_pass_header Set-Cookie;
        proxy_redirect off;
        proxy_set_header Host $host;
    }