edit templates from config page, posted by Stefano Lacaprara on Thu Jun 14 13:12:02 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 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 |
|
Reverse proxy of Elog using Docker and Nginx?, posted by Andrew Wade on Mon Aug 13 21:09:30 2018
|
I've been trying to configured a Synology NAS to run my personal elog with a reverse proxy to the outside world. The best way seems to be running
Elog in a Docker instance and then running a separate connected Docker running a nginx-proxy (in this case jwilder/nginx-proxy).
This second container manages the certificates to letsencrypt and mapping URL requests to relevant containers so that connection is secured properly. |
|
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 |
|
Changing of entries after expired time restriction by synchronisation, posted by Gino Guenzburger on Thu Aug 16 13:33:39 2018
|
I'm working on setting up an elog as lab-journal in our group with the following set-up:
The elog is running on a server, with no back-end access for the users.
Multiple people will use it, all loging in with the
same user-name and password.
The entries submitted to the log-book can only be edited for 24hours, as defined by the "Restrict edit time= |