Howto (prop)set SVN:ignore from the command-line !?

If you’re a developer you’ve probably worked with SVN.

And if you’ve worked with SVN you’ve probably had the problem that it’s commiting and updating more than you want.

So here’s a quick way to ignore the files you dislike:

• If you want to ignore just a file, for example "config.php" from the "config" directory:

svn propset svn:ignore "config.php" /path/to/config

• If you want to ignore all the files in a directory, for example the "cache" directory:

svn propset svn:ignore "*" /path/to/cache

(quick warning here ! "*" is different from "*.*"; the latter implies that you have files or directories with extensions and it will not match a file/dir with no extension)

• If you’re an Apple Fanboy like me than this one’s for you; MacOS has the annoying habbit of creating .DS_Store files in every directory, including those under SVN

edit "~/.subversion/config" with your favorite editor (vi, nano or even TextEdit)

search for the line that contains "global-ignores" and add ".DS_Store" at the end of the row

save it and you’re done; no more .DS_Store junk in your repository !

I hope this quick guide helps you. I’ve written this because most so called coders out there use tools like TortoiseSVN and have no clue how to use SVN from the command line.

If you have other usefull SVN command-line tips, please share them in the comments !

Zend_Growl component proposal

I was browsing the Zend Framework proposals wiki today and I noticed something that caught my eye in the extras incubator: Zend_Growl. For those of you who don’t know, Growl is a protocol and an application for the Mac, which notifies you of certain events. Usually it is used by other Mac applications to pop up an alert, but it can also support TCP / UDP notifications.

This means that you could have a server-side application which could send growl notifications to the user or an admin for monitoring.

I find it very cool and I can’t wait to see it in action !

A new blogging platform

I’m all for lightweight applications. Plus I really really liked the frankness of this guy’s post.

I also have to admit that have problems with other people’s code, but I feel wordpress is particurarly preety bloated.

… and I like the name: it’s almost WoW

So here it is: A new blog

The code is located at http://code.google.com/p/wordcraft

I hope Brian will have time to perfect Wordcraft or at least that I will find the time to also do one blogging platform as I’ve been meaning to for some time now.