rsync

Switched to using rsync to deploy this blog now. Since I re-wrote the blogging software to generate a simple static html site, I needed an easy way to deploy. I was using a Capistrano-esque method of deploying the entire site to dated directories (‘200801142252’, for example), and then I was simply symlinking the public web directory to the most recent release. This has the benefit of being able to quickly roll-back to previous releases (handy when doing major template changes etc), but having to re-deploy the entire site every time I wrote a post wasn’t really very efficient. So I’ve changed it to use the rather brilliant rsync to maintain the site on the webserver now. From my ruby code, I just shell out to rsync as follows:

`rsync -avzr -e ssh #{LOCAL_PATH}/* #{REMOTE_USER}@#{REMOTE_HOST}:#{REMOTE_PATH}`

This runs rsync in verbose, archive mode, using compression, and runs recursively. It specifies the local path, and the remote path for use over ssh (I was using scp over ssh before anyway). It’ll prompt for the password on the command line (although you could setup and specify a key to use with the ssh connection to avoid that). This solution will then keep the local and remote paths in sync, and will mean I can update the blog much more easily and quickly. Hopefully that’ll mean a few more regular posts coming soon… :-)

For all these times, that we walked away

Bit of a catch-up here, as it’s been far too long since I blogged:

  • England are out, and the World Cup is over. The first event left me feeling raw anger towards the Portuguese (who over the years have given me plenty to be pissed about). The second was a rather bittersweet event. On the one hand, I’d far rather see neither France nor Italy win it, but out of the two I would have to have reluctantly picked the aging French surrender monkeys, rather than the greasy match-fixing Italians, to have won it. But the Zidane incident made the entire thing worthwhile, it was pure enjoyment seeing him getting his marching orders, with the classic shot of him leaving the field yards away from the World Cup trophy, combined with the fact than an Italian was for once legitimately polaxed.
  • I got me SkyHD installed, and it is sw-eeeet. I can now watch HD sporting events, movies, and other assorted goodies (including alsorts of random documentaries, which I’d never usually watch except for the fact that it’s in HD). The box itself is sleek and chic, and bar a couple of random lock-ups last couple of days, has behaved excellently for a first generation piece of equipment. Oh, and the Sky+ PVR system is fantastic, I forgot how much I missed being able to setup entire series to be recorded with a couple of remote clicks.
  • I’m wrapping up the add-in architecture for RIDE-ME. I hope to have it in my branch by the end of this weekend, and then merge it over after then to trunk. We can then test the hell out of it, while the other guys start to write whatever add-ins they can dream up. Eventually, in the 1.0 release, it’ll see the light of day, and we hope to build a nice add-in community around it. Oh, and I’m now hosting all of the resources for the RIDE-ME project.
  • Did I mention HD? I’m currently watching Die Hard With A Vengeance apparently in HD (didn’t even realise HD cameras were around back in ‘95), and Bruce Willis never looked so good.
  • I’ve been having a lot of fun with the object/relation mapping framework I’m working on at the minute, integrating it tightly with the model-view-controller framework I knocked together. It’s starting to come together, and I’ve just implemented associations in queries (read: joins). I’ve got a reason for putting all of this together, and that reason is almost ready for the big-time, so watch this space…
  • I’ve ordered a SleepTracker watch, but there’s no stock at the minute so I gotta wait.
  • The new Rise Against album is fantastic, along with the latest albums from Billy Talent and Lostprophets, expect reviews soon
  • RubyCLR is superb, I think John Lam might be a genius
I think that’s mostly it believe it or not, so peace out for now.

Plug In Baby

Here’s a good post from Phil Haack about plugins, and making a plugin architecture resilient to versioning. He presents some good ideas, some stuff worth thinking about in there. I’m thinking about and working on plugins loads at the minute, including working on an add-in architecture for Project RIDE-ME. Reading this post though made me start to question some of the terminology, where a lot of the time I’m using “plugin” out of context. The way I now see it, there are plugins, add-ins, and providers. I’m about to refactor a bit of code I’ve been working on, as it is effectively a provider system, for database and logging providers, however I’ve referred to it throughout as plugins, and I feel this is now slightly out of context…

Plugin: something fairly generic, to be able to “plug in” new components to change almost any aspect of an application
Add-in: something that is contained, used more within rich user interfaces to provide a specific bit of UI content or functionality, much more refined than a general purpose plugin
Provider: some kind of general functionality such as data querying, logging, that can be achieved against different sources, hence the need for differing providers

This is now how I’m starting to formalize some of the terms above, and while almost all of the reflection code remains the same regardless, the design of the architecture depends heavily
on which of the above you are trying to achieve.


Technorati Tags: , , , , , ,

Hi-Def: highly, and definitely, confusing

So I’ve been toying with this post in my head for a few days. I recently bought a Samsung HD Ready 32” LCD TV, and so a week or two ago I decided to get my Mac Mini hooked up to it, using Front Row as a super-duper media center. I soon realised that while the TV touts HDMI/DVI connectors, it really just means HDMI. I’m well aware that essentially, HDMI and DVI are the same signal with different connectors. Why we need two connectors I’m not sure, but certainly DVI-D (completely digital signal) and HDMI are one and the same and so a DVI output from a PC into an HDMI connector will result in a totally digital signal from start to finish.

Now, after my initial disappointment that there wasn’t in fact a DVI connector on the back of the TV, I stuck with VGA (it has a PC input too) until I researched cables and connectors further. I assumed therefore that running using VGA, that HD output from Mac Mini to TV wasn’t possible. I skipped over the fact that the TV picked up on the PC signal, with the Mac switching resolutions to the TV’s native 1366x768 (720p). It didn’t dawn on me that HD could still be possible, as I assumed it needed a digital, not analogue connection.

So onward and upwards… after laughing so hard I thought I was going to break my spleen at the idea of 60 (just over $100 for those across the pond) to buy a gold connector DVI->HDMI cable, I was thinking I’d just give up on the idea, til a trip to eBay came up trumps. 8 (around $14) for a gold connector 2m cable for running from a DVI source to an HDMI connector on a TV. However upon plugging this in and hooking it up to the Mac, it became apparent that the TV and Mac had decided to stop communicating, instead deciding to only offer me some default resolutions (1280x768, 720p, and 1924x1344 or something, equivalent to 1080i). I’ve read that the Intel Mac Mini’s now allow slightly non-default resolutions in order to cater for the native resolutions of TV’s, however I’m out of luck with my PPC Mini (I’ve read about various display tools to achieve the same thing, but am well aware that the wrong settings, especially when talking about refresh rates, can break monitors and TVs).

Long story short, the HD space is crowded with confusion. I’m still not 100% on my thesis that HD will work over VGA or DVI, because its simply based on resolution, so whatever is supported by the TV and output source,will determine if HD is a possibility. I’m still currently using the DVI->HDMI cable, running at 1280x768 (720p), however am not sure if the VGA might provide better quality. And of course, when my Sky HD installation eventually happens (now delayed a further 11 days because of a shortage of boxes), it’ll require the HDMI input, and so I’ll be out of luck unless I buy a switch.

I intended to keep this post shorter than I have, but that pretty much sums up my experience with the integration between HD capable computers and TVs - after all of this, I discovered while playing the test H.264 HD QuickTime videos available from Apple’s website that really my PPC Mac Mini isn’t powerful enough to play HD content anyway - sometimes it just about struggles through, often it chugs and stops and starts making the video, while incredibly detailed, totally unwatchable. I’m now thinking of either a newer Mac Mini, or perhaps even a Windows based media center, more on this later.

It should be said though that Front Row is awesome, and with the Mac also hooked up to my home theatre, I have a simple, elegant way to access and play all of my music collection, as well as the movies, TV shows etc I have stored. It looks truly beautiful on a 32” widescreen TV too.


Technorati Tags: , , , , , , , ,