You could create a branch just before publishing your sites, then run a
script that recursively finds your ".fla .psd" and other files and "svn
rm"'s them from your branch. Then export that branch to your production
sites.
That branch can then live forever as your "March2003SpiffySite" branch,
or you could move it to some other location in your repository to
indicate that it's a final release. Or you could delete it. Whatever.
By the by, the branch, while it looks like a huge waste of space, will
actually only take up a tiny slice of your repository.
Alex Sanderson wrote:
> Dear Subversion users,
>
> We have been using CVS for a long time as part of our deployment solution for
> our websites. There has always been a problem with certain file types that
> we do not want publish online .fla, and .psd files particularly. These file
> types are frequently large so they increase deployment time considerably and
> take disk space on the servers. We really need to store those files
> alongside the jpegs and flashes they are associated with because the tree
> structures always become complex as sites grow.
> Is there a clean way to avoid putting the flash and image sources on our
> production sites? We still need to keep the production sites under version
> control.
> Thanks
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 12 02:25:49 2004