Use Your Mac to Share iCal Calendars
mcwetboy writes "Calendar publishing with iCal requires a .Mac membership or a WebDAV server. Most ISPs and hosting companies don't offer WebDAV -- or at least mine don't -- but you can run WebDAV under Apache on your Mac, and publish calendars and share them among a local network or among multiple users of a single computer. Already two different tutorials explaining how to do this have appeared on the Web: this one at Mac OS X Hints and this one courtesy of Shawn Wall. I'm sure Slashdot readers could offer even more suggestions." I set up mod_dav for the first time within an hour of downloading iCal the other day, with help from this article. Now, if only iCal weren't really slow and buggy ...
I kept getting XML errors when restarting httpd after enabling WebDAV. Turns out it's a conflict between Marc Liyanage's otherwise excellent PHP4 module for OS X.
If you need to run both WebDAV and php, use Apple's php module.
I haven't tried either. Reviews for each (calSync, iCal FTP) on VersionTracker are mixed.
calSync, a shareware application, allows uploading of iCal calendars via FTP instead of webdav. iCal FTP is a freeware app that does the same thing.
I haven't tried either. Reviews for each (calSync, iCal FTP) on VersionTracker are mixed.
It's just copied from here!
Apple has a decent selection of calenders up on their site at . They have lots of great sports and movie release calenders that you can subscribe to for free.
Apple promised WebDAV over SSL in Jaguar, but didn't deliver as far as I can tell. I'm stuck dragging stuff back and forth to Goliath instead of being able to edit it directly in Emacs, and I can't use my secure WebDAV server to share my iCal with only my friends rather than everybody. This is terrifically irritating.
The Calendar Makers Association of America (CMAA) has filed a lawsuit against Apple for promoting the illegal sharing of calenders over the internet.
Said a representative of the CMAA:
"We can not allow the distribution of content without properly compensating the original creators."
T Money
World Domination with a plastic spoon since 1984
For the record, here's another iCal/WebDAV tutorial (via Forwarding Address: OS X ). They're cropping up all over the place, aren't they? Looks like quite a few people have decided that local publishing would be nice to have.
I'd like the ability to view iCals on the web like .Mac lets you do. I already have the webdav server set up a la iDisk (from months ago). However, I need a pretty display program. I really don't have the time to do it myself right now, so are there any perl/php modules that can do this and have it look pretty?
Windows would help too, although I'm not too concerned about that. Oh, and I need to be able to sync it with my Zaurus. Can iCal do this?
Yuo have been trolled.
I was just messin' with you. (and it worked) hehe
(Cancel that "MOD PARENT DOWN").
Anyone figured out how to get this working under tomcat? I activated webdav for tomcat, and when publishing iCal writes a file in the proper directory. But iCal keeps complaining that "Error: Calendar could not be published". Again, there's a file there, so I'm assuming the webdav is working. Is this just a buggy iCal? There are no logs that I can find to help determine what's going wrong ... ?
Brilliant idea. Instead of getting Apache to work, you can spend many "fun" hours banging your head against the wall trying to get Exchange to work (well, as much as it ever does). Exchange will even throw in periodically losing your data, all for "free", after you pay Microsoft for the Exchange license, of course. And then you'll still have trouble sharing your calendar with people who are less moronic than you are. But since you'll be spending so much time fiddling with your software, your calendar won't have any entries in it anyway.
Now that's silly. Outlook doesn't always just work! Who has you brainwashed? iCal is a first version, and it is considerably better than some first version. Still not as useable as it should be.
Since Jaguar has failed to provide the promised WebDAV over SSL support I'd like to get a little more security regarding the control of publishing versions of my calendar file. Since the published calendar is going to be public I'm not too fussed about who can see the file itself but I would like to use something other than Basic Auth to control access so that the password is not sent in the clear.
Has anyone out there got mod_digest or mod_auth_digest to work with the OS 10.2 WebDAV? I'm using Apache 1.3.22 on a Linux server and I either get a "Password mismatch" if I use the older mod_digest or I get and "invalid nonce" error if I use the more recent mod_auth_digest.
If anyone out there has got this working I'd love to know what you did.
If intelligent life is too complex to evolve on its own, who designed God?
probably stupid question as apache on linux may include the same modules, but just in case I will ask. What do people recommend (module wise) for running a webdav server on linux for mac users to access? What is the most compatiable and does Linux apache ship with the same modules as OSX or is their webdav one of their own?
I've experiments to run, there is research to be done on the people who are still alive.
I've launched a little website called iCalShare.com that's a directory of all the cool iCalendars people have made. If you've made a calendar that you want to share with a wider audience, iCalShare.com is the place to do it.
It's also a great place to find a calendar. Some of the calendars listed on the site include calendars for space shuttle launches, Mac tradeshows, Cocoa and WebObjects training courses, and UK Sci-Fi conventions.
Check it out and let me know what you think!
Patrick Crowley
iCalShare.com
Share Your iCalendars!
I love 10.2, but way cant Apple create 1 program that handles email, calender, and addresses.. Now I have 3 programs that I have to use to organize my life - 3 programs which themselves needs organizing.
Apple laptops are effectively unusable for unix users.
I am a long-time Unix user. That means I need to have the Ctrl key to the left of the A key. This is a genuine need , not merely a want; it is based upon ergonomics. The Ctrl key is heavily used in unix, and it must be easily accessable. It cannot be off in the lower left corner of the keyboard where it is difficult to get at, and where it distorts the position of your left hand such that you can't easily type other keys while holding the Ctrl key down.
Apple desktop keyboards are now all USB. They are all OK. The CapsLock key can be re-mapped into a Ctrl key.
Unfortunately, even in this modern age, all Apple laptops have built-in ADB keyboards. The ADB keyboard is broken-by-design. It is, in general, not possible to remap the CapsLock key into a Ctrl key.
There are some exceptions, but they are horrible kludges. They are horrible kludges because the original design of the ADB keyboard was a horrible kludge. The correct solution would be for Apple to re-design their laptop motherboards to use built-in USB keyboards. This hasn't happened yet. If you run Linux, use Debian's solution. For Mac OS X users, uControl works. There are no solutions (that I know of) for either NetBSD or OpenBSD. Please note once again that the "solutions" above are in fact kludges, because of the original bad design of the ADB keyboard.
Apple is (currently) ignoring Unix users! This is not merely speculation on my part. In an on-going email exchange I am having with an Apple employee (whom I won't name) in their marketing department, the Apple marketing person directly stated to me that Apple was catering to their historic Mac customers, and is purposely ignoring the Unix market. He also claimed that Apple would soon start paying more attention to the Unix market. I won't hold my breath. Apple has been ignoring Unix users for more than 10 years. I expect that trend to continue. (Also note that my Apple contact indicated that Macs would never ship with a 3-button mouse, even though Apple intended to port almost all X-window software and deliver it either on a CD/DVD or installed directly on each Mac's hard drive. How Unix friendly is a 1-button mouse with X programs that often require 3 buttons?)
Apple has now lost two opportunities to sell me hardware. I really wanted an Apple laptop for their superior battery life, and for the PowerPC with Altivec CPU. (The Altivec is vastly superior to the x86 line for DSP.) Because I can't live with the broken-by-design built-in ADB keyboard in all Apple laptops, Sony and IBM sold me laptops instead. If Apple fixes this problem, they will sell me a PowerBook next year; if they don't, I'll still be running OpenBSD on x86 hardware, and wishing I could use a Mac.
*ahem*
You mean they're ignoring Solaris users. All normal UNIX vendors have been shipping standard PC keyboards for years. Get with the times. It's not like you're being forced to use Dvorak. Learn where a tilde, a pipe, a backspace key, and a Ctrl key are really supposed to go.