Is this a process from design to testing?

Question

I have an SVN repository. I am developing my web application. Someone manually copies the committed files from the repository to the test environment website, it is checked. If this is good, someone will manually copy it from the test site to the production site.

Is this "supposed"?

EDIT: How about updating svn (read further). Do I use this instead in this process? The problem is that I have to sell this to people who are used to doing things on the server (me too). Trying to convince someone that this is not the way when it has always been so difficult, but I see that as we grow larger, it will be useful. Yes, we know that it is not ideal for this with one copy on the prod server, but I would like to make us more professional in this.

EDIT: I used SVN export to copy from my svn repository to my web server production folders. however, when I did this:

svn export --force file: /// Library / Subversion / Repository / Project1 / Library / WebServer / Documents / MyProject

It is copied along branches, tags, and connecting lines (and then code). How do I get the code? Or should I use all three, like this, and point my web server to trunk / index.php?

This is on mac apache2 snow leopard, if that matters.

Answer 1

In fact, the test part of the repository-> can be optimized and automated. You can set up “copying” so that it happens automatically at night, so that the test group arrives the next morning and immediately starts its work - without copying things around.

Answer 2

Ideally, you will use the ANT task, which will do everything for you.

Basically, you should run this task every time you want to move code between environments.

Good read on ANT expand :