Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Save time with .Mac personal domains and RapidWeaver Apps
A few days ago I read this hint about using .Mac's new Personal Domain feature with other than iWeb-created sites. While the gist of the hint is right on, there are some specifics that weren't mentioned, and in fact there's another, easier way to accomplish the same feat faster. However, you do need to follow the instructions about turing on the domain feature on your .Mac account, and you do need to set up the steps properly with your registrar.

Anyone who uses another program to create sites (such as RapidWeaver, which I use for mine) knows that typically these sites export into a folder all their own. This creates problems, because your personal domain is not going to be looking any deeper than the Web » Sites folder (which resides on your iDisk) for an index.html file, returning the Apple's "Not found" page instead. You can get around this by moving all the files out of the folder RapidWeaver creates, and putting them all into the Sites folder. The problem this creates is that now each time you export, you have to export the whole site, as technically everything's changed, so you lose out on the smart publishing features.

There's a workaround to get RapidWeaver to export to the Web » Sites folder, however. If you go to the Site Setup panel, navigate to the pane to Preview Site in Rapidweaver, and then Browse for the Site folder under Web on your iDisk, when you go to File » Export Changes, RapidWeaver will export the site (and subsequently the changes any time thereafter) directly to the proper folder without any other subfolders mucking it up.

But anyone who dares do this like I did will quickly find that it's dog-slow, even just updating changes. I have no idea why it's so unbearably slow to export to iDisk, when "publishing" to the homepage.mac framework is pretty darned quick, especially since they appear mere folders apart on your iDisk. But here is where the real tip comes in...

If you want to use a personal domain with .Mac, the easiest way to do it is to publish your site like normal to the homepage.mac frameworks like you were probably doing before, then just open your iDisk and drag the files from the top-level Sites folder to the Sites folder under Web. This process is almost instantaneous (since it's just moving from folder to folder on Apple's Servers), so you get the smart publishing benefits of your web program as well as the upload speediness you're used to, but you can have the personal domain goodness of the new web.mac framework!

The catch (there's always a catch) is that for the "smart publishing" to really work, before you publish the next time, you have to go back to the iDisk and move your site files back to the original location (where the program expects them to be), then after the update, move them back again. It's a couple additional steps, but it saves you many, many, many minutes over trying to upload and export folders directly to iDisk.

I think it's one of those "the simplest solution...." type of situations.
  • Currently 3.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (2 votes cast)

Save time with .Mac personal domains and RapidWeaver | 3 comments | Create New Account
Click here to return to the 'Save time with .Mac personal domains and RapidWeaver' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Save time with .Mac personal domains and RapidWeaver
Authored by: mcmikemn on Aug 28, '07 11:33:23AM

I haven't tried this hint yet, but could you copy (instead of move) the published website from the top-level Sites directory to the Sites directory under the Web directory? This takes up double the disk space, obviously, but it means that iWeb will always automatically be able to "smart publish," and you will need to merely copy that newly smart-published folder from the top-level Sites directory to the Sites directory under the Web directory each time.

[ Reply to This | # ]
Save time with .Mac personal domains and RapidWeaver
Authored by: acaltabiano on Aug 28, '07 11:57:02AM
WELL, this hint is only for people who are NOT using iWeb. if you're using iWeb, it already publishes to the framework, making this hint unnecessary. People who use programs like RapidWeaver (me, for instance) aren't allowed to "publish" to this same directory, so we have to "publish" to the homepage frameworks which is housed at that first-level Sites folder (or export to Web>sites, which is slower than molasses, and the reason I brought up the alternative, speedier hint). iWeb will automatically put in where it's supposed to go for personal domain hosting, so if you're using iWeb (which you specifically mentioned in your post), completely disregard this hint & do what you'd normally do, and follow Apple's .Mac instructions to a "T." You'll have speedier uploads anyways and smart publishing, as that's what it was designed to do.

HOWEVER, if I maybe misunderstood your mentioning of iWeb, then the answer is "yes", but with a qualification: it's totally not worth it. Moving the stuff from one folder to another is instantaneous, but COPYING it will take an inordinate amount of time, completely DESTROYING the very time-saving basis of this hint. if you were going to copy it over, you'd almost be better served just exporting it there in the first place.

For anyone interested, I timed it. For my little site I have (, exporting the site to Web>Sites took over 15 minutes. "Publishing" the entire site took about 3.

timing has an awful lot to do with the outcome of a raindance

[ Reply to This | # ]

Save time with .Mac personal domains and RapidWeaver
Authored by: sweth on Aug 29, '07 07:00:10AM
Why not just symlink the exported site to the Sites directory? (If the exported site has to be inside the Sites directory for some reason, you could still just symlink its contents into the Sites directory, a la
$ find Sites/EXPORTDIR -maxdepth 1 ! -path Sites/EXPORTDIR -print0 | xargs -0 -J X ln -s X Sites
. If the top-level entries in EXPORTDIR could change after each export, then you might have to erase all the symlinks after each export with something like
$ find Sites -maxdepth 1 -type l -delete
and recreate them, but it would still probably be a cleaner solution than moving the files into Sites and then moving them back before each export.)

[ Reply to This | # ]