Thanks, I'll have a think about that.
We have just started using a Source Control System and not all the
people in the office are technical so I didn't want to change the way
they currently work. I'll have a chat with them and see if moving the
files on a dev folder would be acceptable.
Richard
On 20/12/05, Ryan Schmidt <subversion-2006Q1@ryandesign.com> wrote:
> On Dec 20, 2005, at 18:06, Richard Lainchbury wrote:
>
> > I've put our websites under version control with subversion.
> >
> > One of the things I'm interested in doing is exporting the site files
> > to a staging server instead of manually uploading the files.
> >
> > The problem is, that we decided that putting all files under source
> > control was the best thing to do so anyone can pick a project easily.
> >
> > Is it possible to excude certain files/directories when doing an
> > export?
>
> Well, no... When you tell Subversion to export a part of a
> repository, it'll export the whole thing.
>
> We have our projects structured this way in our repository:
>
> /svn/
> project1/
> trunk/
> dev/
> web/
> htdocs/
> lib/
> scripts/
> ...
> branches/
> ...
> tags/
> ...
> project2/
> ...
>
> The trunk contains dev and web. Dev contains files we need during
> development, like Photoshop files or Flash files or Word documents,
> but things that aren't part of the web site. The web site is in web.
> Htdocs is the web server document root, lib are libraries the code in
> htdocs includes, and scripts are scripts executed from the command
> line—perhaps in a cronjob. Often there are other directories as well.
>
> When we want to put this on the production web server, obviously the
> stuff in dev is unnecessary, so we just get an export of the web
> directory.
>
> How have you structured your repository such that you need to pick
> and choose which files make up the web site?
>
>
>
Received on Tue Dec 20 19:47:55 2005