read-only elog server, posted by Germano Massullo on Mon Oct 23 15:20:32 2023
|
Good day. I am writing this post to ask how I can turn an elog website into a read-only version that will stay online for historical documention purposes.
I tried to search on Elog documentation but I had no success
Thank you and have a nice day |
Re: read-only elog server, posted by Stefan Ritt on Mon Oct 23 16:15:06 2023
|
Use
Menu commands = List, Find, Help
to remove all command which let you create or edit entries (New, Reply, Edit, ...) |
|
Re: read-only elog server, posted by Bockjoo Kim on Sun Apr 28 14:45:22 2024
|
Hi,
Could you be more specific? Where do I get the 'Menu commands"?
Thanks, |
Re: read-only elog server, posted by Laurent Jean-Rigaud on Mon Apr 29 15:22:37 2024 
|
The menu is the line with available functions, customizable in logbooks config
Also, these are buttons in logbook edit view. |
|
Imagemagick not working on Ubuntu, posted by scott on Wed Apr 24 12:55:25 2024
|
Hi Team,
I have set up Elog on the Ubuntu server using the compile and install method. I have installed ImageMagick and GhostScript along with that. |
|
Re: Imagemagick not working on Ubuntu, posted by Konstantin Olchanski on Thu Apr 25 02:11:08 2024
|
Please see https://daq00.triumf.ca/DaqWiki/index.php/Ubuntu#Enable_elog_PDF_preview
see https://stackoverflow.com/questions/52998331/imagemagick-security-policy-pdf-blocking-conversion
|
Suggestion to update Mac OS X instructions in ELOG Administrator's Guide, posted by Andreas Warburton on Sat Mar 9 17:17:02 2024
|
The section of the ELOG Administrator's Guide https://elog.psi.ch/elog/adminguide.html describing
how to build and install ELOG on a Mac OS X system has worked well for me for several years, even though there have been warnings that the "load"
and "unload" subcommands of the "launchctl" command have been deprecated for some time. After trying my luck again on a new Mac |
|
Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide, posted by Andreas Warburton on Sun Mar 10 04:25:43 2024
|
Here's a more complete/correct set of the updated commands:
sudo launchctl enable system/ch.psi.elogd
sudo launchctl bootstrap system /Library/LaunchDaemons/ch.psi.elogd.plist |
|
Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide, posted by Stefan Ritt on Mon Apr 15 18:05:27 2024
|
Thanks for the info, I updated the adminguide.
Stefan
Andreas |
|
Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide, posted by Andreas Warburton on Tue Apr 16 13:20:01 2024
|
Hi Stefan, Thanks a lot for implementing the updated commands. I noted that there are a few typos that could cause people confusion if not fixed:
In one case, "launchctl" is misspelled.
Confusingly, I think the two lines containing the 'enable' and 'disable' commands use the contiguous text string "system/ch.psi.elogd" |
|
Re: Suggestion to update Mac OS X instructions in ELOG Administrator's Guide, posted by Stefan Ritt on Tue Apr 16 13:31:02 2024
|
Thanks, fixed.
Stefan
Andreas |
Draft saved after ~15 minutes, then anything entered a few hours later is ignored, posted by Celeste Torkzaban on Tue Mar 12 09:12:32 2024
|
Hello,
I've noticed that many times, I start an elog and continue editing adding to a few hours later, then I submit and it deletes everything I
entered after the last time a draft was saved. I paid more attention and saw that it saves a draft after about a few minutes, and if I wait too long before |
|
Re: Draft saved after ~15 minutes, then anything entered a few hours later is ignored, posted by Stefan Ritt on Mon Apr 15 17:53:23 2024
|
That's strange. If you edit a message, indeed a draft is saved every ten seconds or so when you keep typing. In our installations we keep an elog
entry typically open for eight hours, then save it at the end of the shift, and everything works fine. Have you tried playing aournd with your config file,
like "Restrict edit time" or so? Please also make sure you have the current elog version. I sse you have 3.1.3 which is quit old. |
|
Record date isn't set to current date when replying to elogs, posted by Celeste Torkzaban on Tue Mar 12 09:20:14 2024
|
Hello,
I started using the record date feature in one logbook, since we plan to copy over old entries Joplin/Onenote. When starting a new entry, I see
that the record date is automatically set to the current date, but when I reply to an elog, the record date is automatically set to the record date of |
|
Re: Record date isn't set to current date when replying to elogs, posted by Stefan Ritt on Mon Apr 15 17:50:20 2024
|
Have you tried the config option "Preset on reply <attribute> = $date". On a reply, the <attribute> will be preset with the current
date.
Stefan |
today date in template, posted by Stefano Lacaprara on Mon Apr 8 10:49:10 2024
|
Hello,
I am using template for some elogbook entries.
|
|
Re: today date in template, posted by Stefan Ritt on Mon Apr 8 11:27:09 2024
|
This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.
Stefan
|
|
Re: today date in template, posted by Konstantin Olchanski on Tue Apr 9 04:50:28 2024
|
> This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.
but can it be done by javascript injection? load a custom .js or .html file, in this file run javascript code to root down the DOM tree until you
|
|
Re: today date in template, posted by David Pilgram on Tue Apr 9 13:49:51 2024
|
This was given to me by Andreas Luedeke of this parish.
In my elog.cfg file, I have the following:
|
|
Installation with amp on Rocky Linux, posted by Nina Bondarenko on Thu Mar 21 15:23:52 2024
|
Hello all,
I am installing elog on an Rocky Linux instance. Have dependensy problem.
rpm -Uvh elog-latest.el7.x86_64.rpm |
|
Re: Installation with amp on Rocky Linux, posted by Laurent Jean-Rigaud on Thu Mar 21 19:30:49 2024
|
Hi Nina,
The RPM is built with Kerberos (libber*), LDAP (libldap*) and SSL (libssl*) options. These libs are missing on your system, and rpm command does
not take care of dependencies. |
|
Re: Installation with amp on Rocky Linux, posted by Stefan Ritt on Fri Mar 22 07:41:56 2024
|
Is there a way to install all dependencies automatically? Like if I install a package like "emacs" I get a list of dependencies with are automatically
installed:
Dependencies Resolved |
|
Re: Installation with amp on Rocky Linux, posted by Laurent Jean-Rigaud on Sat Mar 23 23:51:37 2024
|
Normally it should work. Requirements are set in SPEC file.
$ rpm -qpi --requires elog-3.1.5-20240226.el7.x86_64.rpm
/bin/sh |
|
Re: Installation with amp on Rocky Linux, posted by scott on Mon Mar 25 10:18:55 2024
|
Is there an RPM available for Rocky 8 or Rocky 9?
And checking over https://elog.psi.ch/elog/download/RPMS/ , only el7 is found. Is that the right place to look for EL8 or EL9 based RPM? |
|
Re: Installation with amp on Rocky Linux, posted by Laurent Jean-Rigaud on Mon Mar 25 10:55:43 2024
|
Hi,
The ELOG website provides new link to RPM packages :
Linux binaries are distributed as RPMs. |
|
Re: Installation with amp on Rocky Linux, posted by scott on Mon Mar 25 16:19:02 2024
|
Hi,
Thanks for the links to EL8/EL9. |
|
Re: Installation with amp on Rocky Linux, posted by Laurent Jean-Rigaud on Mon Mar 25 16:44:03 2024
|
Yes, same build options are used.
But i can not'confirm that they are working as well as on EL7. The tests done by build script on CI/CD are quite simple and limited to
rpm installation, service start and access from cmdline to elog server. |
|
Problem in logging with LDAP and passwd, posted by Stefano Lacaprara on Mon Feb 22 12:29:16 2021
|
Dear experts,
I have a logbook which has authentication as follow
|
|
Re: Problem in logging with LDAP and passwd, posted by Sebastian Schenk on Tue Mar 2 16:03:48 2021
|
Dear Stefano,
the support for the LDAP is limited. As stated in the documentation "on an as-is basis".
|
|
Re: Problem in logging with LDAP and passwd, posted by Laurent Jean-Rigaud on Fri Mar 5 01:43:20 2021
|
Hi,
It seems that ELOG does not support LDAPS but only simple LDAP connection.
|
|
Re: Problem in logging with LDAP and passwd, posted by Sebastian Schenk on Fri Mar 5 13:54:13 2021
|
Hi,
we use the LDAPS connection in our setup and it works without issues.
You have to specify "LDAP server = ldaps://server.tld:port" and normally it uses a different port (636) than insecure LDAP (389). |
|
Re: Problem in logging with LDAP and passwd, posted by Laurent Jean-Rigaud on Sun Mar 14 17:02:49 2021
|
Hi Sebastian,
Nice to hear ! |
|
Re: Problem in logging with LDAP and passwd, posted by scott on Tue Mar 19 16:58:52 2024
|
Hi Stefano,
I also tried to set up LDAP authentication and password file-based authentication using the same settings as yours, which is not working as expected. It |