| 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. |