Subversion commit to update files
Posted: Thu Apr 12, 2007 7:54 pm
Hi,
Our current project has grown to a larger team of developers than we normally work with, all working off of a central testing server in our office. On this server is our basic framework, and the development environments for the applications. I've used other version controls systems before, but this is my first experience with subversion, and I'm wondering how to accomplish this....
I have setup the necessary repositories on the server, and given the proper authentication to the users. Works great. However, since so much of our code is centralized on the server, each person is not working with a local instance of PHP, they are all testing against the development box. When someone makes file changes, and commit's them to the repository, all the delta's are stored in subversion, but the files themselves are not updated. Of course, nobody can test their code this way.
How can I setup subversion so that when files are committed, the actual files are updated so we can test the code that was just written? Isn't this how subversion should work?
Thanks,
Josh
Our current project has grown to a larger team of developers than we normally work with, all working off of a central testing server in our office. On this server is our basic framework, and the development environments for the applications. I've used other version controls systems before, but this is my first experience with subversion, and I'm wondering how to accomplish this....
I have setup the necessary repositories on the server, and given the proper authentication to the users. Works great. However, since so much of our code is centralized on the server, each person is not working with a local instance of PHP, they are all testing against the development box. When someone makes file changes, and commit's them to the repository, all the delta's are stored in subversion, but the files themselves are not updated. Of course, nobody can test their code this way.
How can I setup subversion so that when files are committed, the actual files are updated so we can test the code that was just written? Isn't this how subversion should work?
Thanks,
Josh