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

10.4: Store Aperture libraries on multiple volumes Apps
Tiger only hintQuestion: Would you like to store Aperture Library files across multiple drives?

If your answer is "yes!," then you'll be pleased to know it's quite possible to do so, using symbolic links in the Aperture Library package to point to any folder or project of your choice.

Here's what you need to do:
  1. Open Terminal
  2. Change directory (cd) into the Aperture library -- by default, this is kept in your Pictures folder, so cd ~/Pictures/Aperture Library.aplibrary.
  3. At the desired location within the library, create a symbolic link to a folder: ln -s Target Alias_Name.
  4. Open Aperture, and drag folders/projects from the Aperture Library to the linked-to drive. Note that because the Library spans across multiple drives, moving projects will take longer.
I would suggest using this to link to a folder. Projects can be moved under this within Aperture. Look at the folder you linked to, and you will see the newly moved / created / edited projects.

If you link to a project, then be sure to add .approject to the end of your link. Be careful -- funny things might happen, and it could get confusing because symbolic links are moved, and not the projects themselves. Deleting a linked project in Aperture only deletes the link and not the project itself. On a positive note, working with a linked project is exactly the same as working with a project in the original Aperture Library.

Warning: Do not link to a project in an Aperture Library, or have the same project appear twice in a Library. Editing one might cause data integrity problems.

Here is a possible structure:
  • Aperture Library = ~/Pictures/Aperture Library.aplibrary
  • Folder and Projects on Drive0 = /Volumes/Drive0/Aperture
  • Folder and Projects on Drive1 = /Volumes/Drive1/Aperture
Examples for this Structure:
$ cd ~/Pictures/Aperture Library.aplibrary/
$ ln -s /Volumes/Drive0/Aperture Drive0
$ ln -s /Volumes/Drive1/Aperture Drive1
If the drive is not mounted, then it will appear grayed-out in Aperture. To access a project on this drive, first mount it. Aperture will be able to see it without restarting. However, don't click on it until the drive is mounted, or you might have to restart Aperture to see the project.

Please give this a try and provide feedback in the comments ... but remember: Back up first!!!
    •    
  • Currently 2.00 / 5
  You rated: 4 / 5 (3 votes cast)
 
[9,482 views]  

10.4: Store Aperture libraries on multiple volumes | 6 comments | Create New Account
Click here to return to the '10.4: Store Aperture libraries on multiple volumes' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
IMPORTANT: Spaces need to be escaped!
Authored by: lionel77 on Dec 20, '05 08:20:37PM
Whenever you have spaces in path names you need to escape them if you work in the Terminal.

For example, the command cd ~/Pictures/Aperture Library.aplibrary listed in the hint is interpreted by the shell as cd ~/Pictures/Aperture.
So you want to use cd ~/Pictures/Aperture\ Library.aplibrary instead (note the backslash before the space).

It doen't matter much for the cd command as you will simply get an error message, but when you are creating symbolic links things can get a little messy if you don't properly escape the spaces in the path name.

PS:
Rob, I just noticed that the "To protect special characters such as..." message on the post a comment page is wrong. The code tags actually DON'T protect backslashes and the like. If you want a backslash in the text (regardless of within code tags or not) you need to actually type two backslashes. Another problem is that once you hit preview, one of the two backslashes is removed. I have a feeling that this behavior of the forum software is what is responsible for the absence of backslashes in the original hint.

[ Reply to This | # ]

IMPORTANT: Spaces need to be escaped!
Authored by: sjk on Dec 22, '05 08:13:08PM

Re: I have a feeling that this behavior of the forum software is what is responsible for the absence of backslashes in the original hint.

And in your followup example, too. :-)

I recently posted (again) about that backslash issue after it bit me (again) but didn't get an acknowledgment from Rob (again). :-(

Anyway, I usually recommend putting single-quotes around pathnames that contain spaces instead of using backslashes, like:

cd '~/Pictures/Aperture Library.aplibrary'

... with your example.



[ Reply to This | # ]
IMPORTANT: Spaces need to be escaped!
Authored by: lionel77 on Dec 24, '05 04:08:04AM
Very weird, I could have sworn the backslash was in my post after I had posted it...
Yes, single quotes would also work. I usually avoid them as I think that they tend to make thinks more messy but that might be a subjective thing.

Just out of curiosity, a quick test:
one bs: /
two bs: //
three bs: ///
four bs: ////


[ Reply to This | # ]

Forum software is fixed now
Authored by: lionel77 on Dec 24, '05 04:11:22AM

Looks like the backslash eating behavior of the forum software has been fixed now. Excellent. :)



[ Reply to This | # ]
Forum software is NOT fixed
Authored by: lionel77 on Dec 24, '05 04:19:28AM

Looks like I need some sleep, I confused slashes with backslashes in my earlier test.



[ Reply to This | # ]
backslashes vs. quotes
Authored by: sjk on Dec 30, '05 11:43:22AM
Yes, single quotes would also work. I usually avoid them as I think that they tend to make thinks more messy but that might be a subjective thing.

Yep, personal preference is subjective; backslash-quoted text looks sloppier to me. I'll sometimes use them in interactive shells but avoid unnecessary usage in scripts. And I think experienced shell programmers (those I respect most anyway :-)) recommend using single- or double-quoted strings. Anyway, viewing filenames that contain backslash-quoting is more inefficiently unreadable to me than simply dropping any quotes from each end.

[ Reply to This | # ]