It's been a while since the last release, so trunk is pretty different from the last 'stable' release. It's generally not recommended to run trunk code in a production environment, or if you do, make sure to test it thoroughly for your use cases. One reason that you may wish to avoid trunk code is that long-term problems can crop up, e.g. when upgrading to the next major version, we only support upgrades from older releases and not necessarily development versions.
I would probably recommend testing the most recent release to see if it does the job for you. Regarding how to actually deploy it on the production host, the 'run' script has an 'install' method that can install the various resources in the standard locations (e.g. /usr/local/...), however things like process lifecycle management are left up to the administrator. I would recommend that you do all the testing of your target release (or dev code if you wish) on a non-production host, including the installation using run script, and also whatever scripts you wish to use to start and stop the service, etc. There is not a great deal of documentation about our server outside of the PDF for iCal Server, however this is not targeted at the open source distribution, but rather the integrated distribution that is part of Mac OS X Server. The documentation (in a somewhat tattered state, unfortunately) for the open source distribution is all located here: http://trac.calendarserver.org/ Hope this helps, -dre On Jan 12, 2011, at 1:36 PM, Laurence Popiel wrote: > Now that I'm able to setup ad run the development version, where can I find > documentation on setting up in a small network production environment. I'll > have 8 users, three groups and 8 calendars. Does it install differently and > point to different config files ? > > On Tue, Jan 11, 2011 at 12:51 PM, Andre LaBranche <[email protected]> wrote: > Looks like one of the externally hosted dependencies is failing to > download... will check into it. > > -dre > > On Jan 11, 2011, at 8:38 AM, Guy wrote: > >> Likely new checkins have broken something.. it's always risky running trunk.. >> >> The usual advice here is to pick a revision that works and use that... >> either something from the released branch. Or just check out and use the >> revision that worked for you when you where testing. >> >> --Guy >> >> On 11 Jan 2011, at 16:34, Laurence Popiel wrote: >> >>> I am extremely new to Ubuntu and linux in general. I have installed Ubuntu >>> 10.04 and followed the steps outlined in several postings. After a little >>> trial and error I was able to set up and access the CalendarServer and >>> configure users by modifying the accounts.xml and caldavd-dev.plist. I >>> could connect via iCal and the two iphones in my network. >>> Since i was able to get it up and running I decided to build a server to >>> host the Calendar Server, afp file sharing, samba and use the server for >>> time Machine backups. >>> >>> Using a pentium 4 box I installed Ubuntu 10.04 server and followed these >>> steps: >>> 1) edit /etc/fstab to enable xattrs by adding the “user_xattr” option. >>> >>> e.g. (all on one line): >>> >>> UUID=8f2bb850-0e8f-4d81-bba5-fb93ef9b9990 / ext4 >>> errors=remount-ro,user_xattr 0 1 >>> >>> after doing the above you need to reboot, or “sudo mount / -o remount” >>> >>> 2) sudo apt-get build-dep postgresql >>> >>> 3) sudo apt-get install python-setuptools python-xattr python-twisted >>> subversion curl >>> >>> 4) svn co >>> http://svn.macosforge.org/repository/calendarserver/CalendarServer/trunk >>> CalendarServer >>> >>> 5) cd CalendarServer ; ./run -s >>> >>> when I run ./run -s i get this: >>> >>> Downloading libevent... >>> >>> % Total %Received % Xferd AverageSpeed Time Time Time Current >>> >>> Dload Upload >>> Total Spent Left Speed >>> >>> 0 0 0 0 0 0 0 0 >>> --:--:-- 0:40:24 --:--:-- >>> >>> >>> >>> The previous successful install was revision 6725 and it continued and >>> finished without a hangup. >>> >>> now it is revision 6726 >>> >>> Any ideas as to why it worked without a hitch 4 days ago and now I cant get >>> any further than what you see. >>> >>> >>> >>> _______________________________________________ >>> calendarserver-users mailing list >>> [email protected] >>> http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users >> >> _______________________________________________ >> calendarserver-users mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users > >
_______________________________________________ calendarserver-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
