ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66261
|
Mon Mar 23 22:30:44 2009 |
| Brett Viren | bv@bnl.gov | Question | Linux | 2.7.5 | Re: Storing Elog database files in version control (CVS/SVN/GIT)? |
Brett Viren wrote: | Hi,
Is it possible to store ELOG back-end database files in version control so as to synchronize multiple ELOG
instances?
Has anyone tried it? Any obvious show stoppers to such an approach?
Cheers,
-Brett. |
I asked this before learning about mirroring which sounds like a good thing if we can make it work with SSL. |
66262
|
Tue Mar 24 08:14:48 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.5 | Re: Storing Elog database files in version control (CVS/SVN/GIT)? |
Brett Viren wrote: | Hi,
Is it possible to store ELOG back-end database files in version control so as to synchronize multiple ELOG
instances?
Has anyone tried it? Any obvious show stoppers to such an approach?
Cheers,
-Brett. |
I acknowledge that mirroring through SSL is highly requested, I will try to do my best to implement it. Doing it with version control on the back-end files is not such a good idea. After each synchronization you would have to restart the elogd servers, since they don't realize if the files got changed "under their feet". Furthermore, if you have changes on both sides on different entries for the same day, you have a conflict which you have to solve manually with an editor on the raw files. The elog synchronization works on the entry level, not on the file level. So if two different entries for the same day are changed on both servers, they are combined properly without conflict. Only if the same message got modified on both sides, elog reports a conflict and you have to choose one version or the other. |
65820
|
Thu Apr 10 01:33:07 2008 |
| Peter Freeman | peter_free@gmx.de | Question | Windows | | Re: Sticky entries? |
Peter Freeman wrote: |
Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.
Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.
Have looked arround here, but could not find anything in that direction.
Many thanks for any answer.
Peter
|
Nobody an idea if it is possible? |
65821
|
Thu Apr 10 07:48:08 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Sticky entries? |
Peter Freeman wrote: |
Peter Freeman wrote: |
Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.
Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.
Have looked arround here, but could not find anything in that direction.
Many thanks for any answer.
Peter
|
Nobody an idea if it is possible?
|
Sorry, I overlooked your first question.
Sticky entries are not directly supported, but you can get the same (maybe even better) using following scheme:
- Use an attribute, like the "Type" in the example logbook, and add an option "Sticky"
- Use "quick filter = type". This shows up a filter box on the listing at the top right. If you select "Sticky" there, a listing with all sticky entries will show up.
- Use a different style for such an entry with "Style Type Sticky = background-color:red". This makes all sticky entries show up with a red background. |
65825
|
Fri Apr 11 00:15:42 2008 |
| Peter Freeman | peter_free@gmx.de | Question | Windows | | Re: Sticky entries? |
Stefan Ritt wrote: |
Peter Freeman wrote: |
Peter Freeman wrote: |
Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.
Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.
Have looked arround here, but could not find anything in that direction.
Many thanks for any answer.
Peter
|
Nobody an idea if it is possible?
|
Sorry, I overlooked your first question.
Sticky entries are not directly supported, but you can get the same (maybe even better) using following scheme:
- Use an attribute, like the "Type" in the example logbook, and add an option "Sticky"
- Use "quick filter = type". This shows up a filter box on the listing at the top right. If you select "Sticky" there, a listing with all sticky entries will show up.
- Use a different style for such an entry with "Style Type Sticky = background-color:red". This makes all sticky entries show up with a red background.
|
Danke Stefan, I check it out. |
65826
|
Sat Apr 12 05:21:11 2008 |
| Peter Freeman | peter_free@gmx.de | Question | Windows | | Re: Sticky entries? |
Peter Freeman wrote: |
Stefan Ritt wrote: |
Peter Freeman wrote: |
Peter Freeman wrote: |
Hi, I'm evaluate currently if we can use ELOG as an shiftbook. So far I like ELOG very much, but I got a question.
Is it possible to have sticky message entries? Entries that always show up on top of the others. Thats for important entries that are valit for multiple shifts.
Have looked arround here, but could not find anything in that direction.
Many thanks for any answer.
Peter
|
Nobody an idea if it is possible?
|
Sorry, I overlooked your first question.
Sticky entries are not directly supported, but you can get the same (maybe even better) using following scheme:
- Use an attribute, like the "Type" in the example logbook, and add an option "Sticky"
- Use "quick filter = type". This shows up a filter box on the listing at the top right. If you select "Sticky" there, a listing with all sticky entries will show up.
- Use a different style for such an entry with "Style Type Sticky = background-color:red". This makes all sticky entries show up with a red background.
|
Danke Stefan, I check it out.
|
Hmm, I'd like to use the style command, but it has no effect if I put it into the config. If I understood it right, it should be done this way:
Options Status = Open, Info, Resolved, Suspended, Waiting, Important
Style Status Important = background-color:red
Style Status Resolved = background-color:green
They are just showing up with the default style. Am I doing something wrong?
EDIT: Just downloaded the latest version and now it works. My old one was 2058, BUT, how can I change multiple styles, e.g. background and font color at the same time? Komma does not seem to work and two style lines also not. |
65830
|
Mon Apr 14 08:46:41 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Sticky entries? |
Peter Freeman wrote: |
EDIT: Just downloaded the latest version and now it works. My old one was 2058, BUT, how can I change multiple styles, e.g. background and font color at the same time? Komma does not seem to work and two style lines also not.
|
You can separate them with a semicolon. Just like:
Style Category Info = background-color:lightblue;font-weight:bold
Note that you cannot change the font color, since it is a link, and that is defined in the default.css file under
/* standard link colors and decorations */
a:link { color:#0000FF; text-decoration:none }
a:visited { color:#800080; text-decoration:none }
a:hover { color:#0000FF; text-decoration:underline }
a:active { color:#0000FF; text-decoration:underline }
a:focus { color:#0000FF; text-decoration:underline }
|
66025
|
Thu Oct 30 04:28:05 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Standard login Screen - bottom text |
Barend wrote: |
Hi Stefan.
I have been "playing" around with this great tool and found an interesting "issue" ...
I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".
When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.
When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.
How can I apply my own Bottom Text to the Standard Login Screen ?
Thanks & Regards, Barend
|
By using the configuration option "Bottom Text Login = ..." |
|