Best version control for a one man web app?

Question

I\'m just learning how to do things, and want to start using some sort of version control for a web app.

What\'s most appropriate for deploying a python or php web a

Answer 1

I'm not able to answer the question as asked, because I don't develop on a Linux server.

But maybe this experience has a counterpart in Linux world.

I use a local-on-my-LAN-only IIS server (actually on an old laptop that no longer travels but works as a little server). I have VSS installed on that server too. There is an integration between the IIS Server, the FrontPage extensions on that server, and the VSS.

The upshot is that I can use FrontPage to build and edit my site and build a development image that is always backed up in VSS, and I can check out, check in, and do all of that from within FrontPage.

Now, the way I publish is I take advantage of the sharing capability of VSS so I have a deployment image that shares with the project that is actually an IIS web site. I have a deployment-image directory that I can transfer the latest checked-in material to (material that has not changed is not updated). I then deploy the deployment image to the hosted, public web site using FTP (again, only transfering new and updated files).

I present all of these details to suggest what might be the use-case of interest, even though a different solution approach is needed with Linux.

If I wasn't using a tool that integrated with the web server and also the source control at the server, I could do something similar by checking the VSS material in and out of a local directory and then pushing the updated VSS project to the IIS server web-pages directory hierarchy. The workflow is a little more clumsy. In this case, I would not edit pages directly on the development web server unless I could lock check-in pages as read-only or something.

Does this suggest anything that might be appealing in the Linux server case?