[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: From tags to production?

From: Jay Smith <jaysmailinglist_at_gmail.com>
Date: Mon, 25 Feb 2008 09:21:31 -0500

Got it, thanks!

I was stuck on how to get co to update an already existing directory, but
after reading some posts, I just moved the web site root and have snv create
a new one (is this the right way to do it?).

I co'ed tags/r1.0 to /usr/local/www... and then switched between a couple of
versions, works nicely :)

On Mon, Feb 25, 2008 at 9:03 AM, Andy Levy <andy.levy_at_gmail.com> wrote:

> On Mon, Feb 25, 2008 at 8:58 AM, Jay Smith <jaysmailinglist_at_gmail.com>
> wrote:
> > Hi,
> >
> >
> > I created a repo and the trunk, branch, and tags directories.
> > I imported my site in to the trunk directory.
> > I created a work directory for myself and made it a working copy
> > I modified index.html and committed it to the trunk
> > I created a tag by copying the trunk to the tags dir (named r1.0)
> >
> > This is where I'm stuck... how do I get tag r1.0 to the root of the
> site?
> >
> >
> > I was able to get the content to the root of the site using export...
> but
> > that wouldn't work so well in production.
> >
> > At first I tired using svn update, but that seems to require the root of
> the
> > site be a working directory....
> > I don't want to make the root a working dir, because I don't want the
> tags,
> > trunk and branch directories in there... is there another way?
>
> A working copy can be pulled from *anywhere* on your repository. It
> doesn't need to be (and rarely should it ever be) pointed at the root
> of your repository.
>
> So, check out from the tag URL to your production server. When you
> have a new version, svn switch the server to the next tag's URL, and
> so on.
>
Received on 2008-02-25 15:21:54 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.