Reputation:
I have updated my post according to the clarifications requested below. Thanks a lot.
We have a web application that stores audio, video, and pictures in it.
We didn't consider it before, but the digital files are being committed in and out when we do an svn export (publish). Obviously this isn't a good way to go.
We have a /video folder that has 2 gb of videos that got accidentally uncommitted. What I want to do is have svn manage everything except the video /asset folders.
The videos/images/audio files are uploaded by users of the app. So, we need to be able to roll out a site update without those being overwritten ..
Any thoughts on how we could manage deploying an app that won't overwrite the video/asset folder on export?
Thansk in advance!
Upvotes: 1
Views: 929
Reputation: 9801
Well if I understood this correctly, you have certain resources in your app that are big and can not reasonably be version controlled. I would write a deployment/backup script, that keeps backups of these files, and on deployment, it just copies the newest ones into the right places in the fresh checkout. This can be done by storing/updating and extracting a simple zip(or whatever) archive that stores directories. svn can even be extended by certain events, or hooks to those events. That would enable you to do this completely on automatic. On every checkout, run a script that pulls the media.zip over ftp, extract it with "preserve structure" and "update only".
Upvotes: 1
Reputation: 32082
I don't quite understand. svn (normally) uses an edit/merge/commit flow, not checkin/out. Can you clarify what you mean?
Anyway, can't you just svn:ignore
the user-generated files?
Upvotes: 0