Re: do some changes on .CFG, posted by Andreas Luedeke on Wed Aug 19 15:22:58 2020
|
How are we supposed to give you a hint when you don't post your configuration?
Lahreche
Abdelmadjid wrote:
Thanks, but I'm the Admin of local ELOG. |
Re: field selections persist across new log entries?, posted by Andreas Luedeke on Wed Sep 9 10:33:58 2020
|
It is probably possible, but requires a big of a hack.
Whenever you save a new entry or edit an old one, you run a little shell script
to write the value of this field into a file.
Whenever you create a new entry you read the PRESET value with a shell script from that file.
Here
are the relevant excepts from the documentation: |
|
Re: Insert images slow downs the ELOG, posted by Andreas Luedeke on Sat Sep 12 19:19:02 2020
|
I found the most limiting factor of ELOG to be the file access. ELOG stores all entries in files and therefore has a lot of disk access.
We found that an AFS directory for ELOG is unusable. We tried to store our logbooks on NFS, and it was barely usable but slow. Now we use a local
disk on the server, that works fine. |
|
Re: view connecting account, posted by Andreas Luedeke on Mon Sep 14 17:25:08 2020
|
Yes, you can see that in the logging file, if you turn on logging. You might want to read the manual https://elog.psi.ch/elog/config.html. Here's
the relevant excerpt:
|
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: moving eLog to another computer, posted by Andreas Luedeke on Sat Oct 3 11:08:27 2020
|
you need to copy your logbooks into the "logbooks" directory.
you need to copy your elog.cfg logbook config file to the
new elog folder and reference it at start-up (something like "elogd -c /usr/local/elog/elogd.cfg ...")
Some people modify other
stuff (CSS, java scripts) but if you had you would know what you did. |
|
Re: Field values dependent on other selections, posted by Andreas Luedeke on Fri Oct 23 15:10:54 2020
|
Instead of using three different options you could use the same:
Options Eyepiece = Pentax{a}, TeleVue{b}, Meade{c}
{a} Options Form = 5mm, 20mm, 30mm |
|
Re: Create entry from command line - override Date?, posted by Andreas Luedeke on Tue Oct 27 17:07:00 2020
|
You could transform your entries into the ELOG file format (either XML or CSV) and then use the import function. That would upload the correct dates
from your entries.
If you use the "Orig Date" trick you've proposed, you'll see that datetime fields are stored as seconds of the epoch (since |