Updated default CSS file, posted by Stefan Ritt on Sat May 3 15:10:25 2003  
|
I made a new CSS file, which simulated 3D cells using different border
colors for the four sides of each cell. I plan to put this as the new
default into the distribution. There is also a new ELOG icon. If anyone
has a better one, please post it here!
The attached test.html (elog:/3) show the different classes in the CSS
file, thanks to Etienne Van Caille <etienne.vancaillie@mba.be>. |
Personal Address Book, posted by Stefan Ritt on Mon Mar 22 15:27:07 2004
|
The attached simple elogd.cfg implements a personal address book. Since
version 2.5.2, data can be incorporated into ELOG via the CSV format. This
way I moved my address data from MS Outlook to ELOG.
The address book is sorted according to the attribute "LastName", and the
EmailAddress field is converted into a "" link which can be clicked
to start your email frontend directly. Using the CSV or XML export
functionality, the address book contents can easily be exported to other
programs through the "find" page. |
Peronsal Worklist, posted by Raj on Sat May 20 00:54:42 2006
|
Theme = default
Password file = ######
CSS = tiny.css
Display mode = threaded
Suppress default = 3
Admin user = ######
Self register = 2
Entries per page = 100
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1
Summary lines = 1
Display Email recipients = 0
Title image URL = http://yoursite.com/
Comment = Raj's Worklist
List Display = Edit, ID, Job Description, Location, Status, Date Entered, Date Closed
Thread Display = $Location, $Job Description, $Date Entered, $Date Closed,
#Start Page = ?Status=2-Open&mode=threaded&sort=Location
Start Page = ?wpwd=1&mode=threaded&Status=2-Open&sort=Location
Date Format = %A, %B %d, %Y
Time Format = %A, %B %d, %Y, %H:%M
Message Height = 6
Attributes = Location, Status, Date Entered, Date Closed, Job Description, Author
Type To Do = Time
Type Date Entered = time
Type Date Closed = time
Options Status = 1-To Do{1}, 2-Open{2}, 3-Closed{3}, 4-Suspended{4}
{1} Preset To Do = $Date
{2} Preset Date Entered = $Date
{3} Preset Date Closed = $Date
{4} Preset Date Closed = $Date
Options Location = Sequim, Port Angeles, All, Secaira
Extendable options = Location,
Page Title = Roger's Worklist - $subject
Option Author = Filled In Automatically
Subst Author = $long_name
Menu Commands = Back, New, Edit, Delete, Reply, Find, Select, Copy to, Move to,
Reverse sort = 1
Quick Filter = Location, Status
Subst on reply subject = Re: $Job Description
Thread display = $subject, posted by $author on $Entry time
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author
Quick filter = Date, Category, Status |
Nginx config for CERN SSO, posted by Liam Gaffney on Wed Apr 2 12:47:07 2025
|
For those people who are running an elog instance at CERN and need to "hide" it behind the CERN Single Sign On (SSO), I've attached a working nginx.conf file to be used with OKD/PaaS at CERN.
Ideally, you can then configure the elog similar to the below, which will still allow people to register for individual elogs and be approved by an admin user. The usernames are then the CERN SSO usernames...
;
; admin
;
Admin user = lgaffney
Password file = /elog-nfs-2/ids_sso.passwd
Authentication = Webserver, File
allow password change = 0
Login expiration = 0
Self register = 3
|
Forum, posted by Stefan Ritt on Wed Feb 26 09:45:23 2003
|
This is the configuration of the discussion forum on this server. Special
things are:
- a guest menu so people without an account can read it
- an entry can only be edited by the original author ('restrict edit = 1')
- the author and email attributes are taken from the password file and
cannot be changed by the author, thus to make sure who wrote a specific
entry
- the email notification is sent to all people who registered for it, but
their email address is not contained in the "To:" field
(Omit Email to = 1) so that they don't see each other's email address
(for security reasons). For the 'from' field in the email, my address
is used to that people can hit 'reply' on automatic notifications and
they will reach me.
- The option "Format <attribute>" is used for a compact page display |
Example for accelerator logbook, posted by Stefan Ritt on Wed May 19 00:03:48 2004
|
This is a typical shift logbook, in this case for an accelerator. It
contains following features:
- public read access
- write access only for registered users
- typical attributes for shift logbook
- author and author email get automatically filled in
- no email notification |
Demo Logbook, posted by Stefan Ritt on Wed Feb 26 09:38:43 2003
|
This is the configuration of the 'Demo' logbook coming in the distribution,
it contains only the most basic options. |
Demo Database, posted by Stefan Ritt on Wed Feb 26 10:09:54 2003
|
This is the configuration of the demo database on this server. It is also
very basic, with a few exceptions:
- no message text is used (show text = 0)
- no attachments are used (enable attachments = 0)
- in the message listing page, only certain attributes are displayed
(display search = ...)
This database like implementations work a bit like an Excel worksheet.
Attributes are displayed in grid table, and one can click on the column
titles to sort that column. |
Config Examples (this logbook!), posted by Stefan Ritt on Wed Feb 26 09:24:42 2003
|
This is the configuration from this logbook. There are a few special things:
- it uses the same password file as the 'forum' logbook
- it has a guest menu so that people without an account can read it
- the author and email are automatically taken from the password file
- a 'last revision' gets updated on each edit
- entries can only changed by the origial author ('restrict edit = 1')
- no email notification is sent
Please find the elogd.cfg attached. |
CSS file with German comments, posted by Thomas Salein on Wed May 7 15:27:49 2003
|
Hier noch eine schön einfache CSS-Datei mit deutschen Kommentaren zur
Funktion der Objekte. Kann immerhin helfen, um zu verstehen, wo man etwas
einstellen muss. |
|