Ariejan.net

Is your Rails app secure? Really? Maybe you need to perform a major check-up of your Rails application to make sure.

Here’s a comprehensive list that will take you through the most common mistakes and forgotten security risks in your Rails application.

It’s a great post. Print it, hang it on your wall and create secure Rails apps from now on.

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”:

Most people know what Subversion is and that there’s something called “The Trunk” with code in it. Well, there’s more to your SubVersion repository than you think! This article will discuss how to structure your repository in order for you to take full advantage of Subversion’s possibilities.

As you may have read in my previous Subversion articles the base of your Subversion repository are three directories: branches, tags and trunk.

Each directory in subversion can be checked out seperately. See the examples for more information.

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.

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. It has a release branch named RB-1.0 and current development is going on in the trunk.

A user has submitted a bug report (numbered #3391) against your 1.0 release. Here’s what to do:

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).

After I released iAriejan I got some questions about what plugins I run on Ariejan.net. So, upon your request, here is the full listing.

I’ve included links to all the sites where you can download the plugins.

Note that iAriejan comes bundeled with WP Wetfloor and AJAX Comments.

Hot of the press! CSE-Tool 1.1.0 has been released just a few minutes ago! Grab the code now or check a live demonstration!

Please report any feature, support or bug requests back at the project’s SourceForge page.

Also, if you like CSE-Tool (and want your feature added sooner rather than later) please consider making a small donation to the project to encourage further development and support.

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.

I’m going to show you how to release a simple PHP application from SubVersion as an archive file to my users.

This is just a short note to let you know that CSE-Tool 1.0 has been released.

The CSE-Tool allows you to easily (just copy-paste a few items presented to you by Google) deploy your Custom Search Engine. All you need is a CSE (of course) and optionally a Google Analytics account to track who’s coming by.