File Checkout/Version Control on PHP site -


I have realized that this question has been asked 100times but no one really has found the answer to my questions. .

We have many developers working on the same project. Some use Windows, some use Mac, our server is Linux, and each developer uses a different development application (Dreamweaver, Eclipse, etc.). Each developer is running some kind of Apache / PHP / MYSQL on its own computer, with similar versions of our live server.

We have a live (bug free) site on the server, and our test site (each has its own MySQL database).

What we are seeing

  • Some way to allow developers to 'check out' files from the test site and then work with them After doing 'check in'.

  • We want to be able to log in / check in the date / time and check in

  • We end the trial Would you like to be able to copy the selected folder / files to live site even after doing it?

Developer's command line changes the degree of knowledge, at least not from any experts

Is possibly the GUI version of SVN?

I should also add that this is not an independent option, if these requirements come with a payment solution which is fine.

Any information will be appreciated.

There are two easy tricks for deploying on your "live" site:

1) To view your software, use an SVN client on your "live" site when there are changes to deploy, run the SVN UPDATE command (tell your webserver not to serve files in SSN folders For!)

2) There are two root folders on your "live" site when it's time for deployment, then Export SVN ray folder. In your webserver configuration, change your document root to another folder and restart your web server if there is some unexpected problem in deployment, then simply switch back to the first folder

Generally speaking, you can We want developers to test their changes only in their local environments. When it's time to test the full product, treat your "test" server as your "live" server, ideally use the same methods for deployment.

Find yourself a script jockey that can automate all the deployment for you or use something like springloops.com. By eliminating manual deployment procedures, you will be happy for a long time (this is at 3 o'clock, you think that you have fixed the problem of final deployment, so you go to bed. When you wake up at 12.30 and feel That your site is all morning down ... this happens).

For the GUI, use Spligen for Mac OS X, Turtle SEVN for Windows. In the eclipse, use an assumed svn plugins


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -