I just came across your site and I must say, wow. This is truly one of the most helpful, most easy to understand sites I have ever come across! Thank you for such a great source of info.
My request is a little unique though, and I hope you can help me (as well as others that may find this helpful). Recently I’ve been wanting to recreate the .Mac service but on my Mac and I’ve been looking for some info all over the web but haven’t really found anything useful until I came across this site:
This guy actually does it perfectly it seems except I have no idea what he is talking about when he goes on explaining how he did it
He uses a pure FreeBSD server and so technically everything should be doable in Tiger. If you could take a look at it and translate it into a step by step guide, I think it would really great. I’m fairly certain you would understand his descriptions better than I can.
Thank you for your time and help.
[WM: It’s actually pretty easy. Look at the other comments above which explain how to do the write vs. read only trick. Then, if I were doing this, I’d set up folders like this: /dav/user1, /dav/user2, etc. Then create a password file for each user called user1.pw, user2.pw, etc. Now modify the Apache config files as explained in the tutorial AND the comment and add a full section for each user, e.g. alias /dav/user1, alias /dav/user2, etc. Be sure each points to the correct dav folder and password file. It oughta work like a champ.]]]>
What I mean is it possible to trick the OS (by editing the .hosts file for example) into thinking that it is connecting to Apple’s .mac servers when you are really connecting to your local mini?
I realize this would be a hit to Apple’s .Mac revenue stream, but for advanced users who already have external hosting (because they need mySQL and php for example) plus an isp that gives you server space, .Mac is a waste of money…
[WM: Here’s a link that will show you how to do it.]]]>
[WM: You can’t find it in Finder because system directories are hidden. You’re forgetting the forward slash before ‘etc’ so try cd /etc/httpd and all should be well.]]]>
[WM: Great question. And, no, you weren’t dreaming. This is another very good use of WebDAV. You, as the webmaster, can access your web site using WebDAV and update it from remote locations with a username and password known only by you while others still can use a web browser to view your web site in the usual way with no username/password prompting.
To make this work, you only have to make a slight adjustment in the WebDAV snippet you downloaded and inserted into your Apache config file. First, find the line which reads DAV On. On the very next line, insert the following: Limit PUT POST DELETE PROPFIND PROPPATCH MKCOL COPY MOVE LOCK UNLOCK. Make sure all of the text is on the same line and surround the command with LessThan (< ) and GreaterThan (>) symbols just like those surrounding the Location line. The symbols won’t show up here as part of the command, or I would have included them. Also make sure to use ALL CAPS for the methods which are case-sensitive. Now find the line below this which reads Allow from all. On the very next line, insert the following: /Limit and surround it with LessThan and GreaterThan symbols just like you added for the Limit line inserted above. Save your changes to httpd.conf: Ctrl-X,Y,enter. For the changes to take effect, restart your web server in System Preferences->Sharing. That should accomplish exactly what you wanted. ]]]>
The reason I needed WebDAV was to set up shared calendaring for my company’s intranet. One thing I didn’t see mentioned, that I think would be valuable, is to explain how you can use the combination of WebDAV, iCal, and phpiCalendar to create nifty shared calendars. Now if only Windows users had a better way to upload ical files…….the Firefox calendar extension seems to do a decent job, but it’s no iCal.
Thanks for putting this site together, it’s been invaluable to me. One suggestion for a future topic - using phpLdapAdmin to create shared address books, and user accounts. I’ve been looking for a good tutorial on this topic, and haven’t come across any.]]>
[WM: Be sure you have the permissions set correctly. Remember that once you point to a folder outside the /Library/WebServer/Documents tree, you have to worry about owner, group and permissions for every directory in the heirarchy that leads down to your final destination directory.]]]>
[WM: If you both want to connect to each other, both your friend’s Mac and yours need to have Port 80 open. And both your friend’s router or Airport and yours need to have port 80 redirected to the internal IP address of your respective Macs, e.g. 192.168.0.4 or whatever the internal IP address of each Mac is. And a couple footnotes. Some ISPs change your IP address every second or two. These are so called PPPoE providers like Earthlink in some sections of the U.S. If one of you is using such an ISP, this won’t work until you switch providers. You can learn more in our article here. Or you can check each of your Mac’s IP addresses several times over several minutes by clicking here and see if the IP number changes. If so, you’re dead in the water. If not, read on. Some ISPs block port 80 access to client machines such as your Mac. Can you access a web page on your Mac and your friend’s from the Internet? If so, this isn’t the problem. If not, it is the problem.
If port 80 is blocked, then you can tell Apache to listen on another port such as 81. Read the comments on Nerd Vittles here to learn how to adjust it. The demo web site discussed in our WebDAV client article on Nerd Vittles this week is actually running on Port 81 so you can test it for yourself. Keep in mind that, if you change Apache to port 81, then you’ll need to open port 81 on your Mac firewall and you’ll need to point port 81 to your Mac’s internal IP address on your hardware-based router/firewall. Good luck!]]]>
Awesome site, awesome tips, deserve more recognition.
[WM: Thanks and thanks. As for symbolic link, you don’t need it. Look at the text in the WebDAV snippet and find the line that begins with the word “Alias.” Following /dav is the folder location for WebDAV. This can be any folder on any disk attached to the Mac running your Apache web server. Just be sure the folder permissions are set correctly. Hope this helps.]]]>
She seemed rather annoyed that I wanted to complain and just didn’t care in the least. At least Apple provides a script so it SEEMED like Apple cared… a little.
Don’t waste your time.]]>
However all is not lost, the driver for the Xerox 6100 works just fine in Tiger and gives us mac users access to multiplexing (something the Samsung driver never did)
In order to use the driver you need to install it, make sure the printer is connected and then go to ‘add new printer’ from any print dialogue box.
You’ll get a list showing the CLP500 (hopefully!) and see a drop down box for the driver at the bottom of the page. Select Xerox then select the 6100 model.
Everything (including duplexing) works great after that.]]>