Small studio fileserver
- Started
- Last post
- 14 Responses
- rascuache
Heyup
Just after some advice on a file server and version control for a four-person studio.
I'm currently working on my own, but will be adding two windows users and another mac user to the studio. Last time I had another windows user in, version control was non existent, and passing work to and fro was over complicated.
Just wondered if anyone had any advice on the best gear to use as a file server? I was thinking that a mac mini used as a host machine for Version Cue CS4. Not sure if this will be quick/robust enough though?
Would love to hear any pointers from yous guys (& girls)!
- mydo0
wow what kinda stuff are you working on that 4 people need version software?
we're 12 people running an old bashed up PC desktop as a file/printer server. runs nearly as fast as a local drive.
for file versions we name everything correctly. put things in folders. and if you're not sure you can say "hey, which is the latest version?"
- rascuache0
I guess version control may not be a necessity, I'm good at keeping track of my own work, but I thought it would be the easiest way to keep things in check after adding a few people to the workflow.
The work is nothing special at all, mostly online advertising and publishing.
The last time I worked in a 4-5 person studio, there was no version control whatsoever but it wasn't such a big deal since everyone pretty much worked on their own stuff, and just passed files back and forth manually.
However, my last intern was a total pain in the arse for file naming & storage, so I thought a more solid "this is how the software works" type system would be more effective than me saying "this is how I would like you to do stuff".
- It IS the best way, ignore the silly comment above.NONEIS
- ********0
_
even in a <5 person studio version control is a good idea.
- mydo0
i love it though when i open a fold to find this
design
design1
design1new
designv2
designv2tuesday
designhome
home1
d
d2
fsdflsk1
designv3
designv3final
designv3-final-NEW
designv3-new-FINAL-new-ben-v2
designv3.1-new-FINAL-old version
design 3.2 v3 new old final old new v1
- ********0
_
Don't get me fucking started on poster-FINAL2.psd
- ********0
If you use version control when you're small .. you can grow organically without needing to completely overhaul your system.
- ********0
I heard that GIT is good .. more simple than Subversion.
- if you know the command line then git is good. Otherwise use SVN********
- there are like 4 one word commands to learn, pretty cinch...NONEIS
- if you know the command line then git is good. Otherwise use SVN
- Jordy0
Run that in a local kinda way .. perfect.
Or basically setup your own SVN server .. also there are solutions for that.
- looks interesting, could work on a dedicated machine. thanks for the tip :)rascuache
- This is great...Or Sugar SyncBannedKappa
- Amicus0
I always name files this way
Job number Client Name Job Description DDMMYY Version X.n
every time a client change comes in 'n' changes. If a new concept is called for 'X' changes.
eg.
6969 Playboy March Issue (Cover) 260110 1.1.indd
if I have multiple versions of images they get the same date and version number treatments, but every image has a plain english descriptor anyway. I always leave in any stock photo file names in case I need to track them down in the future.
eg. marshmallows iStock_000005836864XLarge 260110 1.0
Long file names make everything hassle free. :)
- Shit the bed. You can read this stuff quickly and easily?rascuache
- what happens if you want to revise an old version? branches and forks are sometimes necessary********
- why the date? the file already has it.ESKEMA
- If you save files to CD, long filenames are often truncated.********
- each job goes in it's own folder, and yes it is pretty darn quick when you get use to the system. makes searches a dreamAmicus
- revisions to old jobs get a new job number.Amicus
- Burn CDs (or DVDs) in a format that doesn't truncate files. We would burn files to disk only every couple of months anyway with our workflow.Amicus
- mydo0
woah.
my plan is much simpler.
one folder. eg. amicusposter
one file eg. amicusposter.psd
another folder. working files
inside working files is all the shit you should never see - name it how you like. a million files. rarely do you ever need the old versions.- your clients must be awesome, I need old versions all the fucking time.rascuache
- "I've changed my mind, can we go back to how it was before"
EEEUUUUUUGGGGGNNHHHH...rascuache - ah, the wonders of the CHANGE FEE FORM! ... it may help change your reality!vaxorcist
- unfortunately I work in-house :(
I spend at least an hour a day making a sound along the lines of: GGNNNNNNGGGHHrascuache
- Amicus0
mydo... when you work with clients over many years, especially ones who are in more mundane industries thinks evolve slowly and you are constantly referring or updating old jobs.
Also, I like to leave a trail for myself for those days I'm having brain fades. It's also very useful to have this much information easily at hand for client invoice disputes or if a new designer needs to go back to old work. The system is almost foolproof.
btw... the date is in there for those times when you do a search and get the last opened rather than date modified field. (Apple should change this)
- acescence0
If you don't need version control, just a central filestore, look into a NAS unit. you'll get a lot more storage space for the money.
also take a look at pixelnovel timeline for subversion, that might work for you.
- RoyBoyII0
NAS all the way.. cheap..
For under 1k you can have a four drive RAID box with Tb's of storage.
Just need to work out how to manage it remotely..
- hellojeehae0
I just got this. Pretty sweet. I use it with another person.
http://www.buy.com/prod/lacie-1t…