Matilda

After many months of frustration with Typo, I finally bit the bullet and have been spending the past couple of evenings cooking up my replacement called Matilda.

It's nowhere complete, with a lot of things still to add but I eventually hope to push it to the GitHub repository and let others break it apart; but only when I'm happy with it.

To ease the transition I've also been using Google's WebMaster Sitemap tool to track dead 404 links still out there in the ether so they will point to somewhere rather than an error page.

Got logging for any 404's beyond the one's I've countered for so sooner or later things should ease up.

Admin side is a bit simplistic, but usable, need to put in RSS & ATOM feed generators and FeedBurner integration; but so far looking (fingers-crossed) good.

...if anything what took the most time was writting the Typo -> Matilda importer.

Keep you posted,

Today me and Michelle went to see The Sound of Music, really good highly recommend it. You may cringe as soon as you hear 'that' song but get past it, really good!

(Summer Strallen pictured with my fiancee)

Ahh… times are good.

Not much of an article more of a message.

Well if you know I’ve spent the past 2-3 months putting together a neat little rails app called AtomPad , it’s really my take on BaseCamp and is a perfect platform to test my Ruby skills and sharpen my OOP mentality.

So far it’s proven to be pretty useful and today I’ve re-written the Reminders and Lists area to be a bit more AJAX powered. So now you can add, delete, even live-edit items right on the screen just by hovering over them; and all without one single refresh.

Plus you get version control so it records what things you change to your notes, so eventually if your in a team it’ll tell you who changed what, when and maybe why (eventually).

Very intelligent, very powerful and so damn cool.

AJAX + Prototype is most definitely king!

One of the problems you may run into with a project that has been deployed with SVN is choosing what it should ignore so that the production app does not fall over itself.

E.g. accidentally putting log files under version control and then deploying them to the server knowing your box will alter these over time.

So how can you get around this, pretty simple really; but first off try the following commands...

Reverting a Directory

svn revert log/*

This basically tells svn to revert everything in the log directory to it's previous state.

Ignoring .log files

svn propset svn:ignore ".log" log

This tells svn to ignore any .log files within the log directory, so the log files generated on your production box aren't the ones from your laptop.

Ignoring mongrel .pid's

svn propset svn:ignore ".pid" pid

This like the command above will ignore the .pid files generated on your laptop, not taking these to your production box.

Ignoring the contents of a Directory

To go one step more, how about when you want the entire contents of a directory ignored from SVN. So say the photos generated on your production box don't get overwritten from your development laptop.

svn propset svn:ignore '*' photo

Enjoy,