How to properly publish a project from SVN?

A

Alexander2011-03-03 13:20:45

Startups

Alexander, 2011-03-03 13:20:45

There is a project on SVN, there is a web server (on the same server, but it is better not to be attached to this). On a post-commit trigger, the project is published to the web server.
While I did it through svn update, the cons are ".svn" directories everywhere. In general, this is not a problem for a test server, and it can be disabled in .htaccess, but it still turns out ugly.
They suggested the svn export option, but in this case all project files will be overwritten with each commit, which is also not very correct (especially with a large number of developers and frequent commits).
Actually, the question is: maybe there is a more reasonable way to publish the project? Ideally, you would get something like a file-by-file diff: replace this, this and this file, delete this, this and this. Then you can also bind to an external FTP server without fully downloading the project there every time.

Reply

Answer the question

In order to leave comments, you need to log in

5 answer(s)

P

Puma Thailand, 2011-03-04
@0lympian

hudson?

I

Ivan, 2011-03-03
@iSage

You can cross svn export with rsync, for example.

A

Anton, 2011-03-03
@AntonMinsk

Just recently there was a dispute on this topic, we considered the following options:
1. SVN up - fast, convenient, reliable (if you configure access to .svn directories correctly) - I personally, with all my hands "for" - have been using this for more than a year method on "combat" servers
2. SVN Export - in principle, nothing complicated, but there is one "BUT", everything is really overwritten, including what is not needed, as for me - it is not very convenient (changing configs, .htaccess etc.), there is also the problem of forgetting something - we are all people and no one is immune from mechanical errors.
3. Use something like Bamboo (it’s planted), I haven’t looked at it myself, but they say that the thing is flexible and can be configured to raise the svn and other mechanics, all the same configs, updates, etc. etc.

N

Nikolai Vasilchuk, 2011-03-03
@Anonym

+1 for svn up. Set up access to the .svn folders and rejoice.

L

Lazer1999, 2011-03-03
@Lazer1999

Um. I came up with an idea, but I can’t check it now (I don’t have access to my svn at work)
1. Get the list of changed files by revision from svn log, write to the file
2. Set svn export on these files…