diff --git a/checklist.txt b/checklist.txt index 0c995904..699750b3 100755 --- a/checklist.txt +++ b/checklist.txt @@ -9,6 +9,8 @@ On PC4534: - Modify ChangeLog - Add release date to ChangeLog - Do a "make indent" +- Do a "make loc" +- Translate new strings in eloglang.german - c:\elog> cvs commit -m "Version x.x.x" - build xxx diff --git a/doc/ChangeLog b/doc/ChangeLog index 26ae3a52..d5ac5303 100755 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,14 @@ +Version 2.5.0, released January 28th, 2004 +========================================== + +- Implemented mirroring, see new section in config.html +- Updated all translation files with current set of required stings +- Search 'all logbooks' only for current top group +- Changed 'message' to 'entry' consistently +- Removed '{n}' in quick filter and find page list +- Display months on find page localized +- Implemented setlocale() for strftime() + Version 2.4.1, released January 13th, 2004 ========================================== diff --git a/doc/config.html b/doc/config.html index c92b7da0..662e2ebc 100755 --- a/doc/config.html +++ b/doc/config.html @@ -28,6 +28,7 @@ [Access Control] [Flags] [Themes] + [Mirroring] *
+
+Sometimes it can be useful to have the same ELOG logbook on two different computers. This
+might be the case if you travel with your laptop, but want to keep the logbooks from your
+desktop computer on the laptop. The problem is that if you add an entry on your laptop,
+the logbooks on the laptop and the desktop get out of sync. Merging only the ELOG database
+files does not help, since two entries could be made at the same day on the laptop and
+the desktop, which would lead to a conflict in that day's database file.
+
+
+To solve this problem, mirroring was introduced from Version 2.5.0 on. This technology
+allows to synchronize one ELOG server with a number of other servers on a per-entry basis. No
+additional software is needed, only two elogd daemons talking to each other. The synchronization
+can be executed manually or periodically. If entries are changed/added/deleted on both sides,
+they get merged properly during synchronization. In order to minimize network traffic, each
+ELOG server calculates a MD5 checksum for each message, which gets exchanged during synchronization.
+Only when the MD5 checksum differs, entries are transferred.
+
+
+To set-up mirroring, following configuration options are available. They should be put
+into the [global] section of the cofiguration file:
+
+ Home of the Electronic Logbook package by Stefan Ritt
+
+
+
+
+
Mirror server = <URL-list>
+
+This statement specifies one or more mirror servers. Each URL must contain the host, port and
+possible subdirectory of the remote server, as if you would access it through your browser.
+A typical statement looks like:
+
+Mirror server = myhost.mydomain.org:8080, http://another.server.org/elog/
+
+
+The URL should not contain any logbook name, this gets added automatically. The second
+example contains a subdirectory, which is typically used if the elogd daemon runs
+under an Apache proxy. If this statement is present in the configuration file, a new
+menu option "Synchronize" appears on the elog page. Clicking on
+this menu options starts the synchronization:
+
+
+
+On the left side one sees the entry ID's. Entries which are equal locally and remotely
+are not displayed. Here are the rules for synchronization:
+
+
+
elog:123) to the
+local entries are used, since they will point afterwards to the wrong entry.
+
+
+
+Mirror config = 0 | 1
+
+Normally, only the logbook entries are mirrored. One can also mirror the contents
+of the elogd.cfg configuration file for individual logbooks. This can be turned on
+by setting this option to 1. Default is 1.
+Only the individual logbook section is mirrored, not the [global] section. Settings
+which are specific to one server, for example the URL = statement,
+should then be kept in the [global] section, so that they are not mirrored between
+different servers.
+
+Mirror cron = Minute Hour Day Month Weekday
+
+This statement turns on periodic mirroring. The format is similar to the UNIX
+cron command. Each of the five values can either be an
+asterisk, which means all possible values, a comma-separated list or a range.
+It can be explained most easily with examples:
+
+
+
+
+Mirror cron= meaning 0 3 * * * Every night at 3:00
+30 7 1,15 * * At 7:30 every 1st and 15th of a month
+0 12 10 10 * Once a year at 12:00 on my birthday
+0 7-18 * * 1-5 Once every hour from 7:00 to 18:00 from Monday to Friday
+
+
+Valid ranges for each value are:
+
+
+
Minute 0-59
+Hour 0-23
+Day 1-31
+Month 1-12
+Weekday 0-6 with 0=Sunday, 1=Monday, etc.
+
+
+If mirroring is turned on, it is advisable to use the Logfile =
+option to turn on logging, so that one can inspect the logfile to see if the mirroring
+works correctly.
+
+Mirror user = <name>
+
+If periodic mirroring is used via the Mirror cron = statement
+and the remote logbook uses user-level access, this statement specifies the
+user name which is used to log in to the remote logbook. The password is taken from
+the local password file and has to match the password in the remote password file,
+otherwise the access is not allowed. The user name is typical the login name of
+the administrator.
+
+Mirror simulate = 0 | 1
+
+If one wants to try out mirroring without causing any harm, one can turn on this flag.
+During synchronization, entries are compared and necessary transfers are displayed,
+but not executed. Default is 0.
+
+