Re: number of entries in Login user list, posted by Stefan Ritt on Thu Jun 14 13:17:33 2018
|
Well, many arrays based on MAX_N_LIST are created on the heap memory, and if you exceed that, elogd simply crashes. There are compile options to increase
the stack and heap size, but that depends on the operating system and the compiler. The value of 100 has been proven to work everywhere. If you increase
it, you're on your own. |
|
Re: edit templates from config page, posted by Stefan Ritt on Thu Jun 14 13:20:26 2018
|
> Dear all,
> I have some logbook which uses preset text depending on some option values, and uses text files for this.
>
|
|
Re: edit templates from config page, posted by Andreas Luedeke on Thu Jun 14 18:17:07 2018
|
> Dear all,
> I have some logbook which uses preset text depending on some option values, and uses text files for this.
>
|
|
Re: edit templates from config page, posted by Stefan Ritt on Thu Jun 14 19:17:41 2018
|
As always, Andreas has clever ideas. Never thought about this possibility.
Stefan |
|
Re: Entry size too large for email notification, posted by Lars Martin on Fri Jul 13 19:14:21 2018
|
Wouldn't it make sense for ELog (by default) to still notify, but not send the attachments by e-mail if the size limit is reached?
Andreas
Luedeke wrote:
Hi Jacky,
if I read the source code correctly |
|
Re: Reverse proxy of Elog using Docker and Nginx?, posted by Stefan Ritt on Tue Aug 14 06:04:53 2018
|
Have you tried the "URL = ..." statement? This determines you elog redirects if you log in. If you reach elog through a proxy, the URL is a
different one that if you access it directly. In your case the proxy URL might be necessary.
Stefan |
|
Re: Reverse proxy of Elog using Docker and Nginx?, posted by Andrew Wade on Fri Aug 17 22:07:41 2018
|
Yes, I tried setting the URL parameter to the url used by the proxy. It goes to the correct address but that landing is the login page.
Andrew
Stefan |
|
Re: Reverse proxy of Elog using Docker and Nginx?, posted by Stefan Ritt on Mon Aug 20 12:42:24 2018
|
Actually this forum works through an Apache reverse proxy with authentication and it works, so I suspect that the problem has to do with jwilder/nginx-proxy.
Since we don't have this here, all I can propose is that you do debugging yourself. Run elogd with the -v flag so that you see all requests coming
from the user through the proxy. Compare the requests through Apache and Nginx to see if any argumets are stripped or mangled. Upon successful login, elog |