Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Version Control

A

atad6

macrumors regular
Original poster
Jul 7, 2006
155
1
Soon I'm going to be setting up a work environment starting with 3 macs and I was wondering how to go about handling version control of adobe files. The three machines will be used to work on the same projects. I was thinking of using version cue but I'm not sure if that's necessary for a small environment. Also with this setup all the project files would only be saved on the server computer, correct? Would it be possible to also have copies of all the saved revisions on another computer too for backup purposes or is this making too much trouble.

Anyway, if anyone has any suggestions for managing a small work environment or version cue that'd be great. I'm at a bit of a loss about how to handle this setup and want to get a good workflow from the start.
 
i've never used version cue and i actualy kind of think it's an overly complicated effort by Adobe. It just seems unnecissary and i've never found anyone who actually uses it. But, on to your other questions. If i were setting this up, i would do something like this.

3 local macs with cs3, fontagent pro (suitcase fusion if you like it better), and if you want some kind of DAM software, extensis portfolio.

Server, running FontAgent Pro Server, and Portfolio Server. Also have something like Retrospect installed for back-ups to an external HardDrive. That way if your server fails you can just unplug that HD and hook it up to one of the local machines to distribute the files out that need to be worked on.

I would also recommend some type of database server tool for billing and time tracking. FileMaker does this pretty well, so you could install Filemaker on every system and Filemaker Server on your server so it's all the same.

That should cover it. If all your work files are in one area, then there is very little need for version control, because it's all located in one place. It's easier to just figure out a good file structure, than it is to use Version Cue.

-JE
 
It may be overkill, but consider Perforce

You may want to consider Perforce. it's fantastic. It may be overkill but then again, it may not.

You can run it free for a small group. According to their web site: The Perforce Server supports only two users and five client workspaces unless used with a Perforce License.
 
atad6 said:
Soon I'm going to be setting up a work environment starting with 3 macs and I was wondering how to go about handling version control of adobe files.
Click to expand...

Version control? Why wouldn't CVS work for Adobe files? It works well for my .c files. If not that SVN. Both are free and widly used.

Read both of these. CVS was/is the most used but subversion seems to be overtaking it.
http://ximbiot.com/cvs/
http://subversion.tigris.org/
 
ChrisA said:
Version control? Why wouldn't CVS work for Adobe files? It works well for my .c files. If not that SVN. Both are free and widly used.

Read both of these. CVS was/is the most used but subversion seems to be overtaking it.
http://ximbiot.com/cvs/
http://subversion.tigris.org/
Click to expand...

VersionCue is just a front end for SVN with a web based project manager and backup utility.

I use VersionCue for just myself. It's great to save as a version and keep on working. It eliminates the need for myDesign_01.psd myDesign_02.psd etc. It's actually the best thing Adobe has done in years to enhance my workflow.

VersionCue is dead simple to setup and I've not had any problems with it. You setup one computer as the server and then everything connects to that server. The best part is that you can setup projects and enable/disable access to each project as needed. It also allows you to sync the entire project to your local drive and then sync back up when needed. You can also setup auto backups of projects and the entire server.

I honestly think that VC is the best option as it's integrated with all Adobe products and it doesn't require any third party software. You just pop open bridge and you're on your way.
 
Thanks for the suggestions. I think initially I will just try version cue because it's integrated with cs3 and see how it fits in with the workflow.
 
VersionCue is SVN like, but should not replace it

SVN is used for code-based versioning, VersionCue is used for graphic file versioning.

I've been using VersionCue/Bridge for a few months now and have just ran through some initial training for a small office of about 14 individuals ranging from developers to designers to project managers. The graphic file versioning is quite impressive and has saved some re-work already. WebDav ensures connections from a remote location will work flawlessly by simply mounting a project folder like you would a shared drive on your LAN.

The biggest hurdle so far, has been modeling a proper workflow. We use InDesign for documentation quite heavily, and place PSD's in the documents for easy revisioning (these documents are not press-ready by the way). Complaints come in when you have made modifications to the PSD's, and the links do not update in InDesign, because they have not been checked into Bridge and synced with the remote copy.

So, personally I would recommend a Bridge/VC workflow for your graphics files, keeps everything in one place, and keeps your files updated (as long as everyone follows the process!).
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back