This is my first stroll through Open Source, so please forgive my ignorance. I have things working close to the way I want them to work, well except for having a calendar that multiple users can add events to. I think that is a "wait for iCal on Leopard" issue. Of course that may all change when the users start reporting problems or feature requests. ;-) My question is about the location of the calendars and principals. Should they stay in the current test location inside of the twistedcaldav directory or be moved to the location indicated in the caldavd.plist (as opposed to the caldavd-dev.plist). If I deploy this to a server with the current locations will the next or any future builds retain that location or move things as needed? I'm hoping to deploy this at a school for use by 40+ teachers and staff and eventually open it up to the 900+ students. Thanks and Have A Great Day. Rick Davis thePRIMAXgroup http://applehelp.org
Hi Rick, --On September 9, 2006 10:34:12 AM -0400 Rick Davis <roodavis@mac.com> wrote:
This is my first stroll through Open Source, so please forgive my ignorance.
I have things working close to the way I want them to work, well except for having a calendar that multiple users can add events to. I think that is a "wait for iCal on Leopard" issue. Of course that may all change when the users start reporting problems or feature requests. ;-)
My question is about the location of the calendars and principals. Should they stay in the current test location inside of the twistedcaldav directory or be moved to the location indicated in the caldavd.plist (as opposed to the caldavd-dev.plist). If I deploy this to a server with the current locations will the next or any future builds retain that location or move things as needed?
I'm hoping to deploy this at a school for use by 40+ teachers and staff and eventually open it up to the 900+ students.
Thanks and Have A Great Day.
For production use you should point the document root to some place outside of the server distribution. On OS X we default that in caldavd.plist to /Library/CalendarServer/Documents, which follows the convention used by the standard web server install. You will probably also want to use the -i option on the run script to install the server components in their usual 'system' location rather than running it from the distribution directory. That will give you the option of having a running production server installation whilst still being able to work on newer version in the distribution directory. -- Cyrus Daboo
On Sat, September 9, 2006 9:44 am, Cyrus Daboo wrote:
Hi Rick,
--On September 9, 2006 10:34:12 AM -0400 Rick Davis <roodavis@mac.com> wrote:
This is my first stroll through Open Source, so please forgive my ignorance.
I have things working close to the way I want them to work, well except for having a calendar that multiple users can add events to. I think that is a "wait for iCal on Leopard" issue. Of course that may all change when the users start reporting problems or feature requests. ;-)
My question is about the location of the calendars and principals. Should they stay in the current test location inside of the twistedcaldav directory or be moved to the location indicated in the caldavd.plist (as opposed to the caldavd-dev.plist). If I deploy this to a server with the current locations will the next or any future builds retain that location or move things as needed?
I'm hoping to deploy this at a school for use by 40+ teachers and staff and eventually open it up to the 900+ students.
Thanks and Have A Great Day.
For production use you should point the document root to some place outside of the server distribution. On OS X we default that in caldavd.plist to /Library/CalendarServer/Documents, which follows the convention used by the standard web server install.
You will probably also want to use the -i option on the run script to install the server components in their usual 'system' location rather than running it from the distribution directory. That will give you the option of having a running production server installation whilst still being able to work on newer version in the distribution directory.
Since -i requires a dst path what do you recommend? From the looks of the output it would seem that /Library would be the intention. That's also a good bit different from what I know of 10.5 server... Josh -- Josh Wisenbaker U, U, D, D, L, R, L, R, B, A, Start for your server http://www.afp548.com
Try 'sudo run -i /tmp/dst' and see what's installed there. If it looks right to you, install it like so: cd /tmp/dst && sudo pax -pe -rvw . / You could also just write to / directly from the run script. Using a temporary location allows you to create a tar package to install elsewhere. -wsv On Nov 27, 2006, at 12:33 PM, Josh Wisenbaker wrote:
Since -i requires a dst path what do you recommend? From the looks of the output it would seem that /Library would be the intention.
On Nov 27, 2006, at 4:53 PM, Wilfredo Sánchez Vega wrote:
Try 'sudo run -i /tmp/dst' and see what's installed there. If it looks right to you, install it like so:
cd /tmp/dst && sudo pax -pe -rvw . /
You could also just write to / directly from the run script. Using a temporary location allows you to create a tar package to install elsewhere.
I'll give it a try. I got Open Directory integration on Tiger server working today and as soon as I can figure my kerb errors out I'll write it up. (I'll post the kerb errors soon.) Looking in the launchd job plist I can see the intended locations of everything and the caldavd controller. I was just wondering why the - i option installed so differently. I assume that it's that way because of 10.5. Thanks, Josh
-wsv
On Nov 27, 2006, at 12:33 PM, Josh Wisenbaker wrote:
Since -i requires a dst path what do you recommend? From the looks of the output it would seem that /Library would be the intention.
-- Josh Wisenbaker, ACSA http://www.afp548.com Changing the world one server at a time.
On Nov 27, 2006, at 8:38 PM, Josh Wisenbaker wrote:
On Nov 27, 2006, at 4:53 PM, Wilfredo Sánchez Vega wrote:
Try 'sudo run -i /tmp/dst' and see what's installed there. If it looks right to you, install it like so:
cd /tmp/dst && sudo pax -pe -rvw . /
You could also just write to / directly from the run script. Using a temporary location allows you to create a tar package to install elsewhere.
I'll give it a try.
And the results are a bit scattered. Everything is built into a /dst/Library/Frameworks/Python.framework/ Versions/2.4/ structure. Everything All the config files and caldavd scripts point to locations in all of the usual places like /etc and /usr/bin, but nothing was installed there. Josh -- Josh Wisenbaker, ACSA http://www.afp548.com Breaking my server to save yours.
You should probably file a bug. http:// calendarserver.macosforge.org/ -wsv On Nov 27, 2006, at 6:51 PM, Josh Wisenbaker wrote:
On Nov 27, 2006, at 8:38 PM, Josh Wisenbaker wrote:
On Nov 27, 2006, at 4:53 PM, Wilfredo Sánchez Vega wrote:
Try 'sudo run -i /tmp/dst' and see what's installed there. If it looks right to you, install it like so:
cd /tmp/dst && sudo pax -pe -rvw . /
You could also just write to / directly from the run script. Using a temporary location allows you to create a tar package to install elsewhere.
I'll give it a try.
And the results are a bit scattered.
Everything is built into a /dst/Library/Frameworks/Python.framework/ Versions/2.4/ structure. Everything
All the config files and caldavd scripts point to locations in all of the usual places like /etc and /usr/bin, but nothing was installed there.
Josh
-- Josh Wisenbaker, ACSA http://www.afp548.com Breaking my server to save yours.
participants (4)
-
Cyrus Daboo
-
Josh Wisenbaker
-
Rick Davis
-
Wilfredo Sánchez Vega