You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Alex Sanderson <al...@duke-interactive.com> on 2004/03/09 15:05:39 UTC
Avoiding certain files in some checkouts
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
Re: Avoiding certain files in some checkouts
Posted by Robert Guthrie <rg...@pobox.com>.
I just occured to me that you could have a cgi script that interfaces
with subversion's apache module(s). I know very little about them at
the moment, being a newbie and all, but it seems that you could create a
cgi subversion filter that automatically removes the undesireable files
from any branch, while still allowing you to use he standard URLs for
checking out working copies.
Or some kind of post-commit script in subversion which merges changes
from the trunk into a branch that has those undesireable files filtered
out with the "ignore" property (chapter 7 of the subversion book). Then
you have a constantly updated version of your sites ready for "live"
exporting. I don't know that this would work, but it's worth an experiment.
HTH
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Avoiding certain files in some checkouts
Posted by Alex Sanderson <al...@duke-interactive.com>.
Thanks Robert,
It is a good idea and I might see if we can work with that. The problem is
that it is less flexible as it means we must have our staging area at the
same version as our production site at some point. This is rarely the case.
Frequently there will be a small part of the site that can go online now or
maybe even a few files that need to be brought up to date. The staging area
is in general far ahead of the production site and it is almost never all put
online simultaneously. I normally write a bunch of small cgi's for our
project managers to use so that I am out of the loop for site updates.. maybe
I can find some way of automating it using your idea but it is not as easy as
having some sort of "view" of the repository without the .fla's
I really appreciate your ideas, I am just trying to look for the perfect
solution... there must be other people who have this type of problem. Btw I
noticed that svn deals very nicely with branching compared with cvs.
Cheers
Alex
On Tuesday 09 March 2004 16:48, Robert Guthrie wrote:
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Avoiding certain files in some checkouts
Posted by Robert Guthrie <rg...@pobox.com>.
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