Check out the list now!
This is the first post, named “Ruby”, in a series of “Ultimate List of … Resources”. I’m going to compose several lists for different topics I encounter during my development work. To start, I begin with Ruby. Later, I will add “Ultimate Lists” about Ruby on Rails, Subversion, AJAX and some other topics.
Feel free to let me know if I missed an important resource. I’m also open to suggestions about other “Ultimate Lists”.
For now, you’ll have to settle for the “Ultimate List of Ruby Resources”.
My articles about setting up a Ubuntu Development Server (part 1 and part 2) have been very successful.
I’m considering writing a new guide with more up-to-date information on how to setup a development server that allows you (and your team) to develop software, manage source code, track tickets and all that stuff.
What should, according to you, be included in this guide? Please let me know! Just leave a comment and I’ll pick it up.
Also read Part 1 - Subversion.
In this part I will tell you how to install Trac on top of your Subversion repositories on your Ubuntu development server. Trac offers you a wiki, roadmap, tickets (tracking system) and access to your SubVersion repository. All of this is bundeled in a very sexy web interface.
Well, let’s get to work now and get Trac installed. When you’re done you will have trac available for all your Subversion repositories.
Since I’m starting some real work on my final school project, I want to install a Ubuntu development server here at home. I have a Pentium 4 box here that will perform that task.
In this first part I will show you how to install Subversion over WebDAV. All of this will be done in such a way that it’s easy to serve multiple projects at once.
In future parts I will tell you more about installing Trac, FastCGI (with Apache) to host Rails applications and how to use Capistrano to deploy your app properly.
As a developer, there are just some things you can’t do without. I have found that there are three things that I need. Really need. If one of them is missing, I have trouble doing my job properly.
I call them “The Three Corner stones of Developerhood”: ~ 1. Coffee
Most importantly coffee. I just can’t do without it. I don’t drink it to stay awake or anything, but it’s just a warm beverage that keeps me focused and gives me the energy I need to keep working.
I just found out that Google Code is now offering Project Hosting! It’s in the same style as SourceForge, but the Google way!
As a Google user you can create a project with a built-in issue tracker and Subversion repository. And if that’s not all, you can tie in a blog (at Blogger.com is you like) and adiscussion group (on Google Groups, of course).
This is really a nice package Google is offering and it looks like a serious competitor for SourceForge.
I’ve already told you about releasing your project with help from Subversion. Now I want to talk to you about using Subversion to fix bugs in your application.
Fixing bugs can be as easy as fixing a few lines of code or as hard as rewriting a significant portion of your application. Both situations need a different approach from us. Let’s talk about the easy stuff first.
For this example let’s say we have a project.
I’ve seen it lots of times before, but I just added it to Ariejan.net (and the next release of the iAriejan theme). Sometimes there are lots of comments and it’s nice for visitors to see what the official reaction of the blog author is.
Since I haven’t really looked into a plugin or anything, this is just a very simple theme hack.
You can apply it to your current theme with almost no effort at all.
Many projects use SubVersion nowadays to store their project code. I do this also at work, and for my personal projects like CSE-Tool.
The question, however, is how to release your current code properly to the public. You probably don’t want your users to check out your current development code. Either you want them to check out a certain version (release) or you want to present them with a download archive containing the code.