I am running elog under Apache as explained in the administrator's guide. Everything works fine, butmy IT service complains about the elog port being publicly exposed, so I have to fix this. As far as I understand when running under a reverse proxy there's no need for the port to be publiuclyexposed, but I cannot find how to configure the elog server to expose it only locally

Hi all,

I am using the Apache webserver authentication and redirection over http (not https). I have configured it 1:1 as described in the Adminguide. In the elog.cfg I set Authentication = Webserver.

All works fine; the webserver requests an authentication and elog recognizes me correctly.
However, when I close and reopen the browser and log in as a different user, elog does not change the user (tested with Firefox and Edge).
I can only change the user if I use a different browser or restart the elogd (reload is not enough).
The X-Forwarded-User header is set to the correct username - I have checked it with a CustomLog in Apache.

Best regards,
Frank

Hello

I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).

Thanks a lot!

As for my suggestion earlier, now I'm at my computer with working elog. I think that the following four lines (three I guess already there but need alteration for this) need to appear in your elogd.conf file.  The first three should also include any other thing you need to display etc.  I've cut this down to the bear bones, and ... means anything else you want to add. 

Attributes = Die, Organisation, ...
List display = Die, Organisation. ...
Thread display = $Die: $Organisation ...
Preset Die = D_#####

Now the first time you run this, it will give D_00001.  You can edit that to D_00100 and it will increment from there.  You may wish to have two types of user, those who can start a new thread, such as yourself, and others who can contribute but not start a new thread / new Die discussion.

Now it may be that the attribute name you gave D_001 etc can be used where I have used "Die" here, which would appear to give a seemless transition. and perhaps without the need of editing the first new thread.

I have tried these as changes to an existing logbook on my system. and they appeared to work fine. but in my case as a single user, I could always change the Die number, a feature I guess you do not want.  I guess there is a way in the config file, but I'm running out of steam for today.  David.

Or what about the "ticket number" feature?  Every new entry  thread (sorry, confusing terminology on my part) would increment the ticket number by one, and there is no limit as far as I am aware.  This is all explained in the elogd configuration documentation.  

Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in full text search.

Stefan

To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome. 

In my case, I had a number of attributes which had a varied prefix.  For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes.  Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile.  Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes.  In your case suffixes may be better, but I hope you get the point.

Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.