|
|
Save time with .Mac personal domains and RapidWeaver
WELL, this hint is only for people who are NOT using iWeb. if you're using iWeb, it already publishes to the web.mac.com 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 (www.randombob.net), exporting the site to Web>Sites took over 15 minutes. "Publishing" the entire site took about 3. --- |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|