Please help with config, posted by Daniel Sajdyk on Mon Sep 2 12:54:12 2024
|
Hello,
I'm trying to create config file for simple incident logbook. It should has 3 attributes:
source (source of incident) with options:
email
jira_id
ezd_id
Tactics |
|
Looking for version update advice, posted by Patrick Upson on Fri Sep 13 12:02:54 2024
|
I've inherited a position that includes deploying elog for an at-sea mission. Once at sea there's no gauntee of internet connection so I have
to be sure things are going to work before hand. The machines I currently have (we have several backup machines) are running elog version 2.9.2 and
I'm looking for a change log, or feature list to determine if it's safe to update the at-sea laptops to the latest version of elog. |
|
Is the Windows Binary/Installer now compiled for Windows 11?, posted by Frank Baptista on Fri Sep 20 16:24:37 2024
|
Hi all,
Quick question -- I was wondering if the current Windows Binary/Installer is now compiled for compatibility for Windows 11?
I did look through the Forum, but the the answer wasn't really clear. |
Re: Looking for version update advice, posted by Stefan Ritt on Wed Sep 25 13:17:06 2024
|
If 3.1.4 runs safely on your laptop, there should be no problem to update the 2.9.2 one. But first do it on a copy of your logbooks from the at-sea.
The get converted automatically into a newer format but that should be transparent.
On the other hand you don't really need a new system if your old installation works fine and you don't need any of hte new features. |
|
Re: Looking for version update advice, posted by Patrick Upson on Wed Sep 25 13:26:07 2024
|
Thanks. I did eveuntaully find the change log and made the decision to upgrade the at-sea machines. So far the configuration file we update for each
mission still works. I have a copy of the 2.9.2 installer that if something catostrophic happens I can remove the new version and take it back, but I don't
think it'll be a problem. We archive logbooks at the end of a mission, but each mission basically starts from a fresh install like state anyway. |
|
Re: Looking for version update advice, posted by David Pilgram on Wed Sep 25 14:21:33 2024
|
I use linux elog, and if you upgrade to v3.x.x, it's difficult to go back to v2.9.x. This is because the log files get grouped in year sub
directories at v3.x.x.
In 2.9.x, the logfiles are store as (made up example) /home/logfiles/yymmdda.log |
|
Re: Looking for version update advice, posted by Patrick Upson on Wed Sep 25 15:02:16 2024
|
I ran a test (using Windows) and you're correct about the subfolder and file naming. I don't think that'll be an issue, but it's good
to be aware of. If we end up having to revert to 2.9.2 for whatever reason, I think it sould still work fine if what logs we have are just copied up a
directory (i.e /home/logfiles/2023/23mmdda.log ==> /home/logfiles/23mmdda.log) |
|
choosing the default font ? , posted by Pavel Murat on Wed Nov 13 18:12:34 2024
|
Dear All,
is there a way to choose the default "style" for the HTML encoding ? - I'd like to set it to "Typewriter" but couldn't find
the corresponding option in the available docs/ sample config files... |