RSS feed

Linkedin Profile

Tags:
programming
seattle
things that bug me
wall art

Posts by month: 10/08 (2)
08/08 (1)
06/08 (2)
05/08 (1)
03/08 (3)
02/08 (1)
01/08 (2)
12/07 (2)
11/07 (1)
07/07 (1)
05/07 (2)
02/07 (1)
01/07 (1)
12/06 (1)
11/06 (1)
10/06 (1)
08/06 (1)
07/06 (1)
06/06 (2)
05/06 (1)
04/06 (2)
02/06 (1)
01/06 (2)
12/05 (3)
11/05 (2)
09/05 (5)
08/05 (5)
07/05 (7)
06/05 (3)
05/05 (6)
04/05 (8)
03/05 (7)
02/05 (7)
01/05 (6)
12/04 (2)
11/04 (3)
10/04 (5)
09/04 (3)
08/04 (5)
07/04 (5)
06/04 (4)
05/04 (4)
04/04 (9)
03/04 (4)
02/04 (3)
01/04 (5)
12/03 (1)
11/03 (14)
10/03 (8)


Solidity of artefacts vs. solidity of process
2007-12-10

I watched this Clay Shirky video months ago and it stuck in my head. Then it turned up again on IT Conversations on my drive home tonight and it made some more sense.

Any particular system or architecture or project is an edifice. People and culture are a renewable building material.


Rails 2
2007-12-05

I started playing around with Ruby on Rails in late June. I know this because I recorded the date June 30th at the top of my notes titled "Ruby stuff". The "Ruby stuff" page contains the following:

Starting the web server:
	ruby script/server

Creating a new controller:
	ruby script/generate controller controller_name

To run ruby in console mode, run
	ruby script/console {production|development}
	Development is the default if no argument is offered

That's it. I like taking notes when I use some new language or technology so I can come back months later and work out how the heck I ever got whatever-ing to work. In this case, I stopped taking notes after starting console mode. So Ruby on Rails is very easy to program: script/generate creates files ready to be filled up with Ruby; MVC is baked in and the M bit is automated down to the database; Rails provides convenient methods for accessing the model called finders that let me create a type Thing with a name property and then call Thing.find_by_name(…) . And because this is just recreational programming I don't care about perf, I don't even need to know the database is there, or what that dynamic method cost me.

So I went off and wrote some new blog software, and even put in some new features: tags, multiple users, a kml feed (which I will post about later), and an RSS migrator. This was precipitated, btw, by Dominic quitting his .Net hosting.

Back to my notes. The next page is title "Setting up rails app on dreamhost". There is no actual blood, sweat or tear stains on this page, but only because I wiped the monitor down. The page contains the following:

set up the rails app with the command "rails directoryname"
sync the app from svn
change the home directory to /public, wait 10 mins
stand on one foot
edit the fcgi file
kill any dispatch.fcgi processes
stand on the other foot
put the app into production by editing the config file
kill any dispatch.fcgi processes
…

OK so it wasn't quite like that. But it was close. And it took a long time. Apparently Dominic has capistrano deployments working. I guess I need to look into those!

Tags: programming

Back to weblog