Note: the specific subversion information in this post is now out of date. Please refer to the CodeIgniter Downloads page for the latest information.
If you’ve been following the CodeIgniter community, then you’ll know that some time ago, we made an subversion (SVN) repository available. Subversion is a version control system that we use internally to be sure we’re all working from the same page. The SVN is publicly available, and is committed to by 4 of the fine folks at EllisLab. I’ve referred to it before, but I’ve never really talked about how to use it. Recently, there’s been some people interested in getting the latest and greatest CodeIgniter changes pre-release - and heck, why not, as there’s some fine work in there. This post will talk about how you can use the SVN to keep up with the latest CodeIgniter changes.
First of all, the standard disclaimer: we make great efforts to be sure that the code in the repository is bug free and functioning, but as is the case with all “bleeding edge” releases, from time to time things may slip in there, so I don’t recommend you use it in a “mission critical” environment.
In windows? Go for Tortoise SVN. Integrates with Windows Explorer and has probably the most intuitive interface I’ve ever worked with. In any event, pick a client ;)
Now create a folder on your computer somewhere, and rightclick to set up a new repository. As your destination, choose “http://dev.ellislab.com/svn/CodeIgniter/trunk” which is where we keep our stuff. Now your goto command is “update” and “show log”. Update gets you the latest files, and “log” let’s you see what changed. Here’s an example of the log file from today.
Notice that most times when we check something in we make a comment? Sometimes a change is so minor that we don’t bother, but in general it’ll help you stay on top of what is new in the repository.
Changes tend to come in fits and spurts. You might see nothing for two weeks, and then a dozen changes in two days. In general, anything particularly noteworthy will be discussed here (on this blog), so you don’t need to check it every day, but you might want to keep an eye on future changes yourself.
Welcome to the cutting edge! ;)