I am no Windows expert. An option is to write your own application and use the "elog" command to post the output of the application to your ELOG.
There is as well a python library to access ELOG via http: https://github.com/paulscherrerinstitute/py_elog

The elog downloads page is slightly out of date, https://elog.psi.ch/elog/download.html

1) the "git clone" instructions work (but there is no git tags corresponding to different releases, I suggest adding test: "elog developers 
recommend always using latest version from elog git repository").

2) "elog source code", recommends downloading tar file, but latest tar file is from February 2023, probably out of date. people who can compile elog 
from sources can do "git clone", is the "tar" method still relevant?

3) windows binaries, latest available is from 2018, before the famous security fixes, probably no longer safe for running on the open internet. I 
suggest we remove this section and say "sorry, windows binaries no longer available".

4) linux binaries, all links are dead, and we have requested removal of elog packages from red hat, debian and ubuntu. (and they have been removed).

K.O.

Thanks for the reminder, I updated the download instructions.

Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. Thing is I CAN send using other programs, but not with Elog. It is impertive I figure this out or have a work around.. but a 'work around' does not seem like a possible  task since all the work (forums and such) will be via my Elog server.

Thanx, John

ELOG has not change in the last years in that respect, but I know that mailer get more and more picky about encryption etc. So you probably have to convince your mailer to accept the pw as it comes from ELOG, or do not require a pw for that specific client.

Stefan

Dear all, 

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

Wishes, 

M

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.