Re: Using curl to post new entries, posted by Florian Feldbauer on Wed Sep 2 11:56:04 2020
|
After going through the code of the Python API (https://github.com/paulscherrerinstitute/py_elog/blob/master/elog/logbook.py) I tried the following:
$ python3
>>> from passlib.hash import sha256_crypt |
|
Re: Using curl to post new entries, posted by Stefan Ritt on Wed Sep 2 15:42:40 2020
|
This is correct. The elogd daemon needs username and password in parameters "unm" and "upwd". The password must be SHA256 encoded,
so best is to grab it from the password file. This way one does not have to send clear text passwords over the network.
Florian |
Query to get values for Attributes, posted by Florian Feldbauer on Mon Sep 21 09:17:52 2020
|
Hey,
I'm trying to integrate the Elog into our SlowControl System (Phoebus/EPICS). As a first step I translated the python library to Java. So
writing new Entries and viewing them works. |
Re: Query to get values for Attributes, posted by Andreas Luedeke on Mon Sep 21 20:03:49 2020
|
That would be a nice feature...
If you are good in parsing HTML you can achieve this feature: when you create a new entry "<elog-URL>?cmd=new", you'll get
HTML source code that provides you with all possible attribute choices. |
|
Re: Query to get values for Attributes, posted by Florian Feldbauer on Tue Sep 22 09:27:45 2020
|
Thanks for the tipp. I managed to use XPATH to get the values for my Type and Category attributes!
The API, I'm developing for Phoebus is quiet simple. It currently just supports Author, Subject, Type and Category as attributes and the
latter two are just lists of values. |
|
Placeholders in Python API, posted by Florian Feldbauer on Wed Nov 25 15:10:34 2020
|
Hey all,
In the configuration of the Elog one can use
Preset Author = $long_name |
|
length of condition names, posted by Harry Martin on Wed Dec 2 22:45:16 2020
|
The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change
to that rule anywhere in the docs.
I have been using multi-character condition names successfully. I find these are easier to use since they can be more descriptive |
|
Re: Options <...> vs ROptions <...>, posted by Harry Martin on Thu Dec 3 01:51:49 2020
|
Same problem here, in version 3.1.3. It would be very nice if this worked.
Wolfgang
Bayer wrote:
According to section "Syntax of elogd.cfg" of the "Administrator's |