So, with the death of the primary SATA2 HDD in Celcius (it’s what I named the box, based on one of many snowboard/mtb stickers on the chassis), things rolled back a little. Specifically this blog, and my fiance’s photoblog. It’s a case of “not enough time to get it done”, which is a poor excuse in my situation; but shit happens.
The 3.5″ SATA2 HDD was replaced with a 2.5″ SSD rated with an avg Read/Write > 250MB/s. This new SSD syncs important data with the RAID5 housed in the chassis every 3 hours.
Celcius is quieter and using less power so my goal of an absolutely tiny footprint on the net continues. Future upgrades include CPU & RAM (currently using a fantastic AMD Opteron: 90w), and newer HDDs for the RAID (WD Greens maybe, it’s primarily backup & offline access).
I’ve corrected the backup routine with an aggressive rsync.
I’ve recently switched my home server (AMD Opteron 170/4GB ram/hybrid RAID 5/static IP) from Windows (2003->2008->7) to Ubuntu Server 9.04. It’s been a great refresher on Linux, however I forgot about kernel dependency and installed 9.10, and then realized I couldn’t use my RAID card. It was only a few hours of lost time, but it still sucked. Getting 9.04 going took about 20-30mins because I knew what to install, and in what order.
It’s pretty sweet for web app development.
I’ve decided that instead of releasing a standalone version, it’ll become a hosted service/saas. This comes at a cost of more development time, to create the account management/etc. I’m going to allow custom CSS loading, and possibly some kind of online template editing. I’m not sure yet. Lots of ideas. I’m thinking that integrating a Zenfolio account will be the next major iteration.
Starting late on Monday carried over to a late night on Tuesday at work. It was an unexpected, but overall beneficial long day. I’ve managed to squeeze in a little time for refactoring the JavaScript portion of awFlickr app, which I plan to release into a private beta this weekend.
I’ll think of a better name once I get it out for testing. I’m planning on using this as a base for Spiral’s PHP version, and my tentatively named aw:Mail.
This past weekend I started working on a Flickr app that’s REST/JSON/JavaScript based (with a PHP back end generating the JSON). It’s a very old project I never really got started on, but was pretty easy to (almost) complete in under 2 days.
I discovered… a Flickr ID is too large for any web browser JavaScript engine to handle; they rounded up randomly. HTML comments on photos are very annoying from a programmatic point of view. I really like JavaScript.
I used the code base from my portfolio and hacked it up, by taking out the # operations and using events on all the dynamic objects/elements. I also corrected the JSON transportation. Now I’m left with a few visual effects to create, and some misc behavioral changes.
I’m hoping to have v1.0 released this week under the MIT license.
With the new employment at Maple Works Technology, working on Spiral has become very low priority due to other projects and having a fiance. I’m hoping to have a spring beta.
With Christmas having come and gone, and New Years just around the corner; development has slowed to a crawl on Spiral due to a lack of time for this project. It should pick up again in January, after I return from Jamaica where I’m shooting a wedding.
I’m hoping to have a beta up and running on the in-house dev server soon!
I’m using it for the first time with Spiral, and it’s slowing down my planned rapid development cycle. It’s definitely worth learning, and I’m sure it’s going to be worth while based on Spiral’s schema. I’m not sure if I’m a fan of CUD (CRUD?) though, because it complicates things and complains about FK relations sometimes.
Based on this Microsoft TechNet article I’ve refactored the Views used to access Spiral’s data via sproc . This is one of many changes which have allowed for a much broader role for the applicable. Spiral will be released as a community portal.
The database will be deployed as SQLExpress and be cluster ready if you attach it to SQL Server 2005 or newer.
