svn - Need a fool proof way to maintain and update a web application without messing it up -
I am working on a simple social networking application and it will be ready to launch soon. Although I would like a way to maintain it properly as we would like to update from time to time and add new features. I need some points how to do it right now I have my applications to use the conservative SVN on a local server and every time I want to upload it, I export it and our remote server A simple FTP exported on
Is there a better way to do this - I mean I do not want to upload and I have to find out that I'm accidentally overwriting an important file which means no overwrite I mean, what is the proper way to do this.
Web server If no file exists in the repository, then it should not be on the web like this You can easily move the entire web and create extra versions (such as beta versions on a separate domain) without worrying about copying all the necessary files and you can easily create new features without breaking the release version To add - just a different Work on the facilities at the branch, check the branch at a different URL and when you are ready, then merge the branch back into the trunk and update the trunk copy.
Of course, there are some drawbacks to checking the normal working copy on the server, for example there are probably some files that you do not want to serve on the Web. It can be and maybe not a problem - I am working with it, so it does not bother me, because every request goes through the controller stack.
Comments
Post a Comment