svn:ignore is a great way to exclude certain files or folders from being added to your subversion repository. Typically I’ll manage this via an IDE plugin like subclipse (in Eclipse), but if you want to do it via the terminal instead (bash)…here’s how. Crappy way You can add single values to your svn:ignore by running this command either at the root of your project or wherever directory you want the ignore to take effect: ... Read more

I just setup my machine at home with Ubuntu 8.10 (desktop) which was so easy think I saved hours off the time it would normally take with Windows. So much is already installed and ready to go and with apt (or the Synaptic package manager) it’s super quick to download and install extra things things like MySQL, PHP, Apache, Java etc Here are some notes which helped me out when configuring some of these development tools. ... Read more

Setting up “externals” with subversion can assist you when you want to load external libraries into an existing project. You may have a JavaScript validation framework which you re-use amongst many projects. Of course you don’t want to copy and paste the code into every project, what would happen then if you wanted to upgrade the codebase? Using subclipse (in the Eclipse IDE) you can link a separate svn repository in the middle of your project by adding an svn:externals property. ... Read more

Most developers who use Source Code Management are familiar with the fact that while you can have any directory you want in your ‘repositories’, it is recommended that you use the following directories as a base layout: branches tags trunk The trunk directory will hold the “main line” of development, a branches directory will have “branch-ing” development (perhaps a maintenance release?), and a tags directory holds a “snapshot” in time (essentially a read-only area) often used when deploying to a production server. ... Read more