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

Re: Web projects (not the VS stuff) and correct post-commit

From: Michiel van Oosterhout <michiel1978_at_hotmail.com>
Date: 2004-09-22 23:50:08 CEST

----- Original Message -----
From: "Brian Mathis" <bmathis@directedge.com>
To: "Michiel van Oosterhout" <michiel1978@hotmail.com>
Cc: <users@subversion.tigris.org>
Sent: Wednesday, September 22, 2004 6:53 PM
Subject: Re: Web projects (not the VS stuff) and correct post-commit

> Michiel van Oosterhout wrote:
> > Hello,
> >
> > I'm a newbie on subversion. I want to store webprojects in repositories
on a
> > win2k computer which runs apache with virtual hosts for each website. I
> > develop on another machine in the network. I am confused how to do this,
> > because the repository is in a special files (Berkeley DB), so I can't
have
> > that as documentroot. Check out to local, edit, commit. Then a hook on
> > post-commit to update the repository to the documentroot? That would
mean
> > that for every minor edit I should commit to see the result on the
server.
> > That would be a bit much. Any tips, or FAQS on this? I am not currently
> > using VS, I use dreamweaver.
> >
> > Thanks
> > /M
>
> A typical setup that you would use for something like this would be to
> have 2 completely different environments, production and development.
>
> The development area would have it's own web server and working copy on
> it. The dev web server would allow the development directory to be
> accessable via the web. You check out your working copy from the
> repository, then make all your changes to those files, but don't commit
> each little change. Then, when you're satisfied with all the changes
> you've made, you commit them to the repos. After that commit, you
> update the version that's on the production server. Sometimes those
> changes will be small (spelling errors maybe), and other times big.

Well, in my situation, the production server is at a host. So I couldn't
directly checkout to it, because I have to ftp the files.So perhaps a
checkout to a local directory from the repos on the dev server and then FTP
to the host?

And the dev server would contain some repositories and also some virtual
hosts, right? Could I checkout from the repos on the server to the virtual
root on the server, from my pc on the network (with dreamweaver of VS)?

And for developpers that are outside my network, can they do that as well?
So they work on the files in the virtual root (with me) and update the svn
now and then. I'm thinking along the way of webdav or?

Many questions, because I want to understand the best way from others'
experience before I start setting it up.

Many thanks!

Michiel

>
> Svn is a tool that gives you many more abilities, but it doesn't come
> for free. You'll need to put forth a little more effort to use it.
> After you do it a few times, you won't really notice it though. In the
> end, it's well worth it.
>
> --
> Brian Mathis
> http://directedge.com/b/
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 22 23:56:34 2004

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