Fell calserver users, I'm finally getting back to something that's been on my to-do list for awhile--setting up the cal server for my family to use. I know that there are at least a few others out there who do something similar, so I'm looking for feedback on how you've set it up. I'm trying to decide if I want to have an account--and, thus, potentially multiple calendars--per person, or if I want to have just one account with multiple calendars under that account. The advantage of the latter layout is that it most accurately mirrors what we have right now. Access control isn't a big issue, because right now it's only my wife and I managing calendars related to ourselves and other members of the family. The advantage of the former layout, though, is that it scales better for the future (when kids manage their own calendars) and allows more segregation of activities into different calendars. It also would allow for kids to be able to manage their own calendars, but not change those of the parents. I can manage the technical details pretty well on my own (so far), but am looking for feedback on the administrative side of things. Any and all help appreciated. Thanks! -cj --- Chris Cleeland
This idea really appeals to me personally and I'll be watching this thread; but I can't help but see the humor in it as well. Little Jimmy, I can't take you to soccer practice because you didn't schedule it on your calendar! What? Your Vista Outlook install isn't syncing with the BSD CalDAV server? Well, use the web interface to schedule a time for Dad to debug it. It's not your Mother's fault that you insisted on having a Dell Windows laptop. :) Isaac Vetter Chris Cleeland wrote:
Fellow calserver users,
I'm finally getting back to something that's been on my to-do list for awhile--setting up the cal server for my family to use. I know that there are at least a few others out there who do something similar, so I'm looking for feedback on how you've set it up.
I'm trying to decide if I want to have an account--and, thus, potentially multiple calendars--per person, or if I want to have just one account with multiple calendars under that account. The advantage of the latter layout is that it most accurately mirrors what we have right now. Access control isn't a big issue, because right now it's only my wife and I managing calendars related to ourselves and other members of the family.
The advantage of the former layout, though, is that it scales better for the future (when kids manage their own calendars) and allows more segregation of activities into different calendars. It also would allow for kids to be able to manage their own calendars, but not change those of the parents.
I can manage the technical details pretty well on my own (so far), but am looking for feedback on the administrative side of things. Any and all help appreciated.
Thanks! -cj
--- Chris Cleeland
On Apr 7, 2008, at 9:35 AM, Isaac Vetter wrote:
Little Jimmy, I can't take you to soccer practice because you didn't schedule it on your calendar! What? Your Vista Outlook install isn't syncing with the BSD CalDAV server? Well, use the web interface to schedule a time for Dad to debug it. It's not your Mother's fault that you insisted on having a Dell Windows laptop.
There will be no Dell in the house, nor Outlook. The IT Staff refuses to support it. Either OS X or Linux, depending on situation.
:)
:) :) --- Chris Cleeland
Hi Isaac, --On April 7, 2008 10:35:57 AM -0400 Isaac Vetter <ivetter@math.purdue.edu> wrote:
This idea really appeals to me personally and I'll be watching this thread; but I can't help but see the humor in it as well.
Little Jimmy, I can't take you to soccer practice because you didn't schedule it on your calendar! What? Your Vista Outlook install isn't syncing with the BSD CalDAV server? Well, use the web interface to schedule a time for Dad to debug it. It's not your Mother's fault that you insisted on having a Dell Windows laptop.
:)
Yes, but think of the advantages when the kids are older and fighting over access to e.g. a car! Parents will just have to say "whoever has it booked on the calendar, gets it"! Of course one could also have a resource calendar for every toy in the house, but that would probably be taking things too far :-) -- Cyrus Daboo
Hi Chris, --On April 7, 2008 9:20:48 AM -0500 Chris Cleeland <chris@milodesigns.com> wrote:
I'm finally getting back to something that's been on my to-do list for awhile--setting up the cal server for my family to use. I know that there are at least a few others out there who do something similar, so I'm looking for feedback on how you've set it up.
I think I can fairly lay claim to the fact that my family is the first to use CalDAV on the basis that we have been using it since 2005 in one guise or another. I do actually run OS X server at home with CalDAV enabled. Having shared calendars etc is the big benefit for us.
I'm trying to decide if I want to have an account--and, thus, potentially multiple calendars--per person, or if I want to have just one account with multiple calendars under that account. The advantage of the latter layout is that it most accurately mirrors what we have right now. Access control isn't a big issue, because right now it's only my wife and I managing calendars related to ourselves and other members of the family.
I have separate accounts for each family member just because that's how the server as a whole is setup for email, ichat etc. My wife and I are read-write proxies for the kids (they are too young to use computers) and we are each read-only proxies of each other. I also set up a family group calendar (that is tied to the wikiserver feature on OS X server too) and that has a calendar for public holidays (one for US, one for UK). The whole setup works pretty well with the exception that we can't currently sync the proxied calendars over to our respective iPhones.
The advantage of the former layout, though, is that it scales better for the future (when kids manage their own calendars) and allows more segregation of activities into different calendars. It also would allow for kids to be able to manage their own calendars, but not change those of the parents.
Yes.
I can manage the technical details pretty well on my own (so far), but am looking for feedback on the administrative side of things. Any and all help appreciated.
If you have or are going to have separate accounts for other things like email, im etc, then I think it makes sense to stick with that for calendars too - particularly if you can share the same authentication db etc. -- Cyrus Daboo
Thanks for all the quick replies! On Apr 7, 2008, at 9:35 AM, Cyrus Daboo wrote:
--On April 7, 2008 9:20:48 AM -0500 Chris Cleeland <chris@milodesigns.com
wrote:
I'm finally getting back to something that's been on my to-do list for awhile--setting up the cal server for my family to use. I know that there are at least a few others out there who do something similar, so I'm looking for feedback on how you've set it up.
I think I can fairly lay claim to the fact that my family is the first to use CalDAV on the basis that we have been using it since 2005 in one guise or another. I do actually run OS X server at home with CalDAV enabled. Having shared calendars etc is the big benefit for us.
It seems appropriate that you would have this deployed at home! It also reassures me that it will be able to support the needs of a family (as well as an enterprise).
I have separate accounts for each family member just because that's how the server as a whole is setup for email, ichat etc. My wife and I are read-write proxies for the kids (they are too young to use computers) and we are each read-only proxies of each other. I also set up a family group calendar (that is tied to the wikiserver feature on OS X server too) and that has a calendar for public holidays (one for US, one for UK).
I don't have OS X server, and hence can't run an OpenDirectory (though I would dearly like to). If you could only use the XML directory, would you still have a setup like this (per-user calendars)? Also, in regard to your group calendar, who owns that? The group (of which you are all members)? Also, I should point out that I actually want my wife and myself to have write access on at least some of our calendars. We often end up scheduling things for the other and need to capture that somehow.
If you have or are going to have separate accounts for other things like email, im etc, then I think it makes sense to stick with that for calendars too - particularly if you can share the same authentication db etc.
Definitely separate accounts for email and the like, although right now we do not have a unified open directory type of thing. In fact, all the machines are relatively standalone and I only physically keep them semi-sync'd in terms of having accounts. Most of the machines are laptops, and in my past experiences, laptops don't fare well when they're tethered to "enterprise" authentication systems. Perhaps leopard (or OS X) is better about that--all my past experience was with Windows and its ilk, YP/NIS/NIS+, and NetInfo, all which became particularly unhappy when they couldn't find their respective masters, and often required administrative trickery to get them to behave away from the enterprise. --- Chris Cleeland
I JUST setup a similar setup. We each have our own calendar users. I made my wife and I superusers for CalendarServer so we can easily see everyones schedules and write to them. By default though they are read only (in Lightning) for the other person, but that can be changed simply by a checkbox. CalendarServer is running on a Fedora Core 8 box, and we use Windows XP, Vista and OSX. We sync the iphones using iCal. The one part that is really missing is web support. I just requested to open a sourceforge project to create a PHP CalDAV class. I think a well written PHP CalDAV class will help other Calendar projects integrate CalDAV support into their projects quickly. If there are any PHP developers that would like to assist, here is the URL. http://sourceforge.net/projects/php-caldav/
Hi, assuming your using xml for directory service would you mind publishing an example of (sanatized of course) how you set up super and regular users? I haven't been able to understand how this is established and what part the sudoers.plist file plays. I have everything else working just fine. Thanks, On Apr 7, 2008, at 8:30 AM, Michael J. Pawlowsky wrote:
I JUST setup a similar setup.
We each have our own calendar users. I made my wife and I superusers for CalendarServer so we can easily see everyones schedules and write to them. By default though they are read only (in Lightning) for the other person, but that can be changed simply by a checkbox.
CalendarServer is running on a Fedora Core 8 box, and we use Windows XP, Vista and OSX. We sync the iphones using iCal.
The one part that is really missing is web support. I just requested to open a sourceforge project to create a PHP CalDAV class. I think a well written PHP CalDAV class will help other Calendar projects integrate CalDAV support into their projects quickly.
If there are any PHP developers that would like to assist, here is the URL. http://sourceforge.net/projects/php-caldav/
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
Scott Buchanan wrote:
Hi,
assuming your using xml for directory service would you mind publishing an example of (sanatized of course) how you set up super and regular users? I haven't been able to understand how this is established and what part the sudoers.plist file plays. I have everything else working just fine.
I should have said "AdminPricipals". It is in caldavd.plist I have re-arranged all my files location to be more in line with a Fedora distribution. I might even create an rpm out of it at one point. The next thing I need to do now is write a init.d startup script for caldavd. Unless someone else already has one they can post. <!-- Principals with "DAV:all" access (relative URLs) --> <key>AdminPrincipals</key> <array> <string>/principals/__uids__/mikep/</string> <string>/principals/__uids__/kris/</string> </array> And the accounts.xml looks like: (The guid's really should be uuidgen's but since it is just for us 3, I think we will be ok. :) <accounts realm="Family Calendar"> <user> <uid>mikep</uid> <guid>mikep</guid> <password>xxxx</password> <name>Michael Pawlowsky</name> <cuaddr>mailto:mikep@xxxxxx.net</cuaddr> </user> <user> <uid>kris</uid> <guid>kris</guid> <password>xxxxxxx</password> <name>Christine Caron</name> <cuaddr>mailto:kris@xxxxxx.com</cuaddr> </user> <user> <uid>michelle</uid> <guid>michelle</guid> <password>xxxxxx</password> <name>Michelle Caron-Pawlowsky</name> <cuaddr>mailto:michelle@xxxxxx.com</cuaddr> </user> <group> <uid>family</uid> <guid>family</guid> <password>xxxxxx</password> <name>Family Group</name> <members> <member type="users">mikep</member> <member type="users">kris</member> <member type="users">michelle</member> </members> </group>
Thanks so much. I hadn't tumbled on that. On Apr 7, 2008, at 8:56 AM, Michael J. Pawlowsky wrote:
Scott Buchanan wrote:
Hi,
assuming your using xml for directory service would you mind publishing an example of (sanatized of course) how you set up super and regular users? I haven't been able to understand how this is established and what part the sudoers.plist file plays. I have everything else working just fine.
I should have said "AdminPricipals". It is in caldavd.plist I have re-arranged all my files location to be more in line with a Fedora distribution. I might even create an rpm out of it at one point. The next thing I need to do now is write a init.d startup script for caldavd. Unless someone else already has one they can post.
<!-- Principals with "DAV:all" access (relative URLs) --> <key>AdminPrincipals</key> <array> <string>/principals/__uids__/mikep/</string> <string>/principals/__uids__/kris/</string> </array>
And the accounts.xml looks like: (The guid's really should be uuidgen's but since it is just for us 3, I think we will be ok. :)
<accounts realm="Family Calendar">
<user> <uid>mikep</uid> <guid>mikep</guid> <password>xxxx</password> <name>Michael Pawlowsky</name> <cuaddr>mailto:mikep@xxxxxx.net</cuaddr> </user>
<user> <uid>kris</uid> <guid>kris</guid> <password>xxxxxxx</password> <name>Christine Caron</name> <cuaddr>mailto:kris@xxxxxx.com</cuaddr> </user>
<user> <uid>michelle</uid> <guid>michelle</guid> <password>xxxxxx</password> <name>Michelle Caron-Pawlowsky</name> <cuaddr>mailto:michelle@xxxxxx.com</cuaddr> </user>
<group> <uid>family</uid> <guid>family</guid> <password>xxxxxx</password> <name>Family Group</name> <members> <member type="users">mikep</member> <member type="users">kris</member> <member type="users">michelle</member> </members> </group>
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
Should this work with a CS using OD for authentication? I've edited the caldavd.plist file to put in several OD members as AdminPrincipals (/principals/users/scott/ for example) and don't see them now have {DAV:}all access. I even deleted all files in the Documents root and let them rebuild. Also, where are the ACL's maintained? (what file(s))? On Apr 7, 2008, at 9:00 AM, Scott Buchanan wrote:
Thanks so much. I hadn't tumbled on that. On Apr 7, 2008, at 8:56 AM, Michael J. Pawlowsky wrote:
Scott Buchanan wrote:
Hi,
assuming your using xml for directory service would you mind publishing an example of (sanatized of course) how you set up super and regular users? I haven't been able to understand how this is established and what part the sudoers.plist file plays. I have everything else working just fine.
I should have said "AdminPricipals". It is in caldavd.plist I have re-arranged all my files location to be more in line with a Fedora distribution. I might even create an rpm out of it at one point. The next thing I need to do now is write a init.d startup script for caldavd. Unless someone else already has one they can post.
<!-- Principals with "DAV:all" access (relative URLs) --> <key>AdminPrincipals</key> <array> <string>/principals/__uids__/mikep/</string> <string>/principals/__uids__/kris/</string> </array>
And the accounts.xml looks like: (The guid's really should be uuidgen's but since it is just for us 3, I think we will be ok. :)
<accounts realm="Family Calendar">
<user> <uid>mikep</uid> <guid>mikep</guid> <password>xxxx</password> <name>Michael Pawlowsky</name> <cuaddr>mailto:mikep@xxxxxx.net</cuaddr> </user>
<user> <uid>kris</uid> <guid>kris</guid> <password>xxxxxxx</password> <name>Christine Caron</name> <cuaddr>mailto:kris@xxxxxx.com</cuaddr> </user>
<user> <uid>michelle</uid> <guid>michelle</guid> <password>xxxxxx</password> <name>Michelle Caron-Pawlowsky</name> <cuaddr>mailto:michelle@xxxxxx.com</cuaddr> </user>
<group> <uid>family</uid> <guid>family</guid> <password>xxxxxx</password> <name>Family Group</name> <members> <member type="users">mikep</member> <member type="users">kris</member> <member type="users">michelle</member> </members> </group>
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/calendarserver-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 09:20 -0500 4/7/2008, Chris Cleeland wrote:
I'm trying to decide if I want to have an account--and, thus, potentially multiple calendars--per person, or if I want to have just one account with multiple calendars under that account.
There are no kids in our household, so there aren't the same issues with shenanigans, but what my wife and I have found is that the single access account with multiple calendars is the way to go for us. Much easier to set things up on multiple computers that way. -----BEGIN PGP SIGNATURE----- Version: 9.8.2.3005 wj8DBQFH+jI9DlQHnMkeAWMRAjAcAJ927kkkT4DsjBwD7+VGS52DFc7+/gCgudoZ U7aYflo96dyfcMjf8do4wnQ= =peP/ -----END PGP SIGNATURE----- -- Julian Y. Koh <mailto:kohster@northwestern.edu> Network Engineer <phone:847-467-5780> Telecommunications and Network Services Northwestern University PGP Public Key:<http://bt.ittns.northwestern.edu/julian/pgppubkey.html>
participants (6)
-
Chris Cleeland
-
Cyrus Daboo
-
Isaac Vetter
-
Julian Y. Koh
-
Michael J. Pawlowsky
-
Scott Buchanan