On Fri, 2012-03-02 at 09:47 -0700, steve roush wrote:
I am interested in setting up a family addressbook server and have a
few questions about the syncevolution http server as documented by the
HTTP server HOWTO wiki page.
For each user (device), do I repeat steps 4 through 7 (from the
How-To) - with appropriate changes to parameters/variables?
There are two alternatives:
1. create a separate account for each family member and run one
syncevo-http-server per user, with different port numbers
2. use a common account and configure different databases for each
family member
I'm only mentioning option 1 for the sake of completeness. It's pretty
inconvenient, so better go for option 2.
Do family members share some databases? I would use the default address
book, calendar, etc for the shared databases. The instructions in the
HOWTO work as described for the shared data.
If you want private data for each family member, then add more
databases:
syncevolution --configure \
--source-property type=file:text/calendar:2.0 \
--source-property evolutionsource=file://${datapath}/calendar_john \
${peer} calendar_john
When creating the config for a device owned by John, enable
"calendar_john" instead of "calendar":
syncevolution --configure \
--source-property sync=none \
${peer} calendar
syncevolution --configure \
--source-property sync=two-way \
--source-property uri=calendar \
${peer} calendar_john
Or enable "calendar" as in the HOWTO and just add "calendar_john",
without the "calendar" uri alias. Then in John's client, configure the
URI "calendar" for the shared calendar and "calendar_john" for the
private one. SyncEvolution clients allow that, see "Synchronizing
additional databases" in
http://syncevolution.org/wiki/synchronizing-evolution-http-howto
I assume I can manage the entries by adding, deleting, and changing
files in the addressbook directory.
If so,
- What file format(s) are allowed?
vCard 3.0 and iCalendar 2.0 when using the types mentioned in the HOWTO.
It's also possible to configure vCard 2.1 and vCalendar 1.0, but better
don't do that. In particular vCalendar 1.0 is limited.
- Will the directory and/or files be locked during a synch to
prevent
failures?
No. If you want locking, then use SyncEvolution's command line options
(--import/update/delete-items) to manipulate items. See
http://syncevolution.org/documentation/syncevolution-usage
- Any special instructions (gotchas) regarding maintaining the
files
in the addressbook?
Note that vCard 3.0 must use the property extensions as defined by
Evolution. Other extensions will not be synchronized, but should be
preserved when updating an item (untested!).
Is this information already available & I just missed it?
No, you haven't missed anything. Congratulations, you are breaking new
ground here :-)
If you get it working, then it would be useful to write a HOWTO about
it, or extend one of the existing ones.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.