Re: Icon comment, posted by Uwe on Mon Dec 3 11:25:54 2007
|
Stefan Ritt wrote: |
Uwe wrote: |
one idea for improvement. When using the option 'Icon comment' this comment is shown when creating a new entry and moving with he mouse over the icon but it is not displayed in full or summary view. In full or summary view the filename is shown. Not really important, but perhaps an improvement.
|
I implemented this request in SVN revision #1974.
|
Thank you!
Uwe |
email subject, posted by Bill Whiting on Fri Mar 7 13:44:34 2008
|
Can I control the content of the Subject on an email notification?
i.e. Can I copy the subject from the elog entry into the email subject?
Thanks,
//Bill |
Re: email subject, posted by Bill Whiting on Fri Mar 7 14:09:40 2008
|
Bill Whiting wrote: |
Can I control the content of the Subject on an email notification?
i.e. Can I copy the subject from the elog entry into the email subject?
Thanks,
//Bill
|
I found the answer in the docs.
In the config file add
Use Email Subject = Added Text: $subject
This results in the e-mail subject being set to "Added Text: elogentry subject line"
Thanks for a great tool! |
insert screenshots directly to elog?, posted by harley on Wed Feb 3 21:54:41 2010
|
Elog is excellent!
I apologize for the naive question, but is there a way to insert screenshots directly into elog entries? |
Re: insert screenshots directly to elog?, posted by Yoshio Imai on Fri Feb 5 14:51:23 2010
|
Since elog is only the web server providing (comfortable) access to the logbook database, it relies on the web browser (possibly enhanced by script code) for facilities to attach pictures and other files to entries. So unless your browser has such an extension or someone writes some sort of script that can do it, the only way is to use an external capturing program, save the picture and upload it in the usual way. Cf. also entry 66004.
|
What *exactly* do "clone" and "mirror" do?, posted by David McKee on Thu Jul 22 00:31:54 2010
|
We have been hosting logbook far (geographically and in internet hops) from our experimental site. Recently we have (finally!) gotten reliable on-site internet, and would like to host the log book on-site.
I have a suspicion that some combination of the -C, -m, and -M flags will allow me to migrate the logbook automagically and with a minimum risk of trouble from concurrent operation on the logbook, and to maintain the existing version as a mirror of the new official on-site version. But documentation is not being very helpful. Can someone say a few more words about what these options do?
I've been experimenting as I compose this and have a suggestion for language that might be useful somewhere in the documentation:
In this context "to clone" means to copy the configuration file and all data files associated with a log book so that I can host an identical logbook on a new host (that is this is the command to migrate a logbook). After cloning the two installation are identical, but no effort is made to keep them so: if you continue to run both copies post made to one will not be reflected in the other.
Is this correct?
I'm still not clear on what the -m and -M options do. |
Re: What *exactly* do "clone" and "mirror" do?, posted by Stefan Ritt on Wed Jul 28 16:55:32 2010
|
David McKee wrote: |
We have been hosting logbook far (geographically and in internet hops) from our experimental site. Recently we have (finally!) gotten reliable on-site internet, and would like to host the log book on-site.
I have a suspicion that some combination of the -C, -m, and -M flags will allow me to migrate the logbook automagically and with a minimum risk of trouble from concurrent operation on the logbook, and to maintain the existing version as a mirror of the new official on-site version. But documentation is not being very helpful. Can someone say a few more words about what these options do?
I've been experimenting as I compose this and have a suggestion for language that might be useful somewhere in the documentation:
In this context "to clone" means to copy the configuration file and all data files associated with a log book so that I can host an identical logbook on a new host (that is this is the command to migrate a logbook). After cloning the two installation are identical, but no effort is made to keep them so: if you continue to run both copies post made to one will not be reflected in the other.
Is this correct?
I'm still not clear on what the -m and -M options do.
|
Yes this is correct. But actually you do not necessarily need that. If you want to migrate a logbook to another server, you can just copy over the elog directory containing the configuration file and the logbooks. That's it. Mirroring now means manually triggered or periodic synchronization between two servers to keep the logbooks in sync. Like if an entry is entered on one server, it gets copied over to the other server automatically. That works in both directions. The periodic mirroring can be done using the options "Mirror server" and "Mirror cron" in the configuration files. It can be manually triggered using the "-m" and "-M" flags. But I guess in your case it's enough to copy over the elog tree just once. |
HELP - URGENT - odd ELOG behaviour, posted by Sara Vanini on Wed Jun 1 15:05:59 2011
|
|