Subversion ... is it practical with the PHP framework or not?
I am developing a website using CodeIgniter and PHP. Some of my friends suggest that I start using Subversion to take care of my organization. Can anyone give me a basic explanation of what SVN is jargon-free and also if it's practical for a framework where 5 files are needed to run a single page?
source to share
Subversion allows you to keep your source code in a central location, make changes from multiple locations (eg laptop, desktop), track changes, and revert changes back to the source tree if needed.
Have you ever made a big "improvement" and then decided you were going in the wrong direction? With Subversion, you can revert to a version of your source before heading in the wrong direction.
Or how about that you make some subtle changes to your codebase, but you don't notice that you introduced a new bug until much later. You can use subversion to revert to previous versions of your code, helping you track down the changes that made the error.
This is more valuable when sharing a source with multiple developers, but even for my individual developer projects, I find it very convenient to have all my sources and changes in the Subversion repository.
If you combine it with Trac, you can track bugs / features, breakpoints, and use the Trac Wiki to document your project.
source to share
Every single project (even with one developer) should be under source control, no matter what framework or language you are using.
Using simple words, Subversion will keep a history of your code files if you want to revert them or restore a copy in the event of a disk failure (in which case the SVN must be on a different machine). It will also help you easily see the differences between the two versions of the file.
For more information, just read the TortoiseSVN user manual, it has a pretty good overview of Subversion.
Here's some good information: Chapter 2. Basic concepts
source to share
SVN is a version control system. It is used as a central repository for all your code.
The significant strength of SVN is that it uses the Copy-Modify-Merge workflow model versus the Lock-Modify-Unlock model. The idea is that each developer will check or copy (copy) their version of the code, work on (modify) it, test it, and reconcile any changes (merges) that might conflict with other work done by another developer.
This is really handy, as if you wanted to work on a part of your code, you don't have to worry about the file being locked because someone is working on it.
In any case, developers should use SVN to catalog all versions of their code and revert back as needed.
source to share
SVN is a version control system - which means that it keeps various previous versions of a given file and allows many people to work on the same file, and eventually change all changes together. It will also help you revert to a previous version, if needed.
You should use this in your project if there are many people working on the project. But even if you only have one, it will be easier to manage the project if it is under version control.
source to share
This is a way to keep version control. You might think of this as some kind of additional backup. You submit your code to the SVN server and only keep the differences from the latest version. This way you can downgrade to an earlier version if you need it. It also allows you to work with more people and smooth out differences easily. I say you should use it. It's easy and helpful.
source to share
No matter what software you make, and even if you are on your own, SVN should be used. I depend on it every day. Its the only software tool I couldn't live with. If you can install it off site, it will give you a backup as well.
Simple things like being able to diff on a previous version of a file when changes are made can be of great help.
Use Toortoise under client-side windows. It integrates with Windows and is great to use.
source to share