Just read the manual: https://elog.psi.ch/elog/adminguide.html

> is there an instruction document how to exacly host the ELOG on a server for example a raspberry pi?

would be same as on any other linux machine, in the nutshell:

- install generic raspbian (R-12 is current version)
- setup the network
- setup apache2 https with automatic https certificate renewal using certbot
- setup apache2 redirect to elogd port 8080
- setup elogd on port localhost:8080

some of this is written up here:
https://daq00.triumf.ca/DaqWiki/index.php/Ubuntu#Install_apache_httpd_proxy_for_midas_and_elog

in theory you can run elogd without apache https proxy, but I find computer security
people are quite happy when I tell them that I run apache https with SSLlabs score "A+".

also I believe elogd does not support automatic https certificate renewal, running
it behind apache https solves that.

another consideration, specifically for RaspberryPi, they use SD flash for storage,
and unlike SATA and NVMe SSDs, SD flash does not have SMART to report flash read,
write and wear-out problems. So you may run into unexpected SD flash failures. We do.

do daily/hourly rsync to backup/archive storage to avoid total data loss if this happens.

also be aware that SD flash is very slow, compared to normal PC SSDs. read speed is not too
bad, but write speed is quite abysmal.

as solution to this, RPi5 can have a PCIe/NVMe dongle, you can try that instead of SD flash.

K.O.

Hello. We are using explicity subdir names on our elog server to manage a large number of "Top groups" and sub "groups". When we create a new logbook from a template in the same group, it would be beneficial to automatically give a new subdir based on the previous one. At the very least, it should not reuse the same parameter as the template (see below).

At the moment, it copies the subdir parameter from the template logbook, which results in the new logbook writing to the same location as the template. That is very confusing and has the potential to be harmful as people can (and recently did) decide to delete these "duplicate" entries. But they are not duplicates, they are the exact same entries as the template logbook and deleting them removes them forever!

The way around this at the moment is to manually update the subdir after copying, but then the logbooks need to be re-indexed before the new logbook will display correctly. That requires a manual restart of the elogd process, which is less than ideal. 

So this never made it into the download area ?  elog-latest.tar is elog-3.1.5-1 and contains no files from 2024 or 2025 .

Thanks
 

I stopped making tar files, since most people building elog from sources just pull it from the bitbucket repository:

$ git clone https://bitbucket.org/ritt/elog --recursive
$ cd elog
$ mkdir build; cd build;
$ cmake ..; make

Hi all,

I'm experiencing an issue on Kubuntu 24.04 where the WYSIWYG editor (in HTML mode) doesn't appear at all. This happens across multiple browsers (tested with Firefox and Chromium). The editor area is simply blank, without any visible toolbar or editable content area.

Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!

Thanks in advance,
Pawel

Hi Pawel, I *think* we (you) need the 'ckeditor' program installed on your system for it to work. I am

Hi John,

Thanks for the message! I’ve downloaded CKEditor version 4.22, since newer versions are no longer fully open source and come with restrictive licensing.  I now have the full CKEditor 4.22 package locally, but I’m not quite sure what the next step is. Should I place it somewhere specific in the ELOG directory structure or modify one of the templates to enable it? Any pointers on how to connect it properly to ELOG would be very helpful.

Best regards,
Pawel