Jonathan's Pancheria: Category technical

100x100 Challenge: January 30, Day 2-150 lines

Jonathan Altman — Sat, 31 Jan 2009 06:32:00 +0000

Summary

I did not think I would actually make today one of the 100 days, but I pushed through. I guess the incentive of challenging myself is working ;-)

Accomplishments

Finished debugging the last part of adding the second controlled list admin table. Add and remove working
Added the third and final admin table
Committed

Issues

Ready to move on past admin page. Data for the main part of the application can now be entered and things are ready to move to building the main part of the app now.

LOC counts are harder if you don’t commit your code every day. I will have to figure out how I can reconcile committing the done LOCs versus not breaking the build, as it were. I believe using git’s staging capability will be important for doing that, or I might have to go to trunk and a stable branch, or I can use git clone and keep unstable local and my remote repos stable. Any way will teach me more about git, but it will be easier to manage the tasks of this challenge and the requirements of good codebase hygiene to figure one of them out.

100x100 Challenge: January 29, Day 1-119 lines

Jonathan Altman — Fri, 30 Jan 2009 05:11:00 +0000

Summary

After having to make the day I thought up the idea be my Prologue, January 29 turned out to be fairly easy to make 100 lines of code. Not every day will be this easy, I bet. I also know that I opted for get things done over polish things to perfection. There is definitely some code that should be factored out and made common, but the pattern hasn’t emerged to my brain yet. But the functionality has definitely moved forward

Accomplishments

So here are the accomplishments today:

Moved a little forward on getting Google App Engine SDK debuggable in NetBeans. I’m pretty sure what I’ve done is leading me down a blind alley and will end up being scrapped, but I can now start up my app in the Google App Engine SDK from inside NetBeans. But breakpoints clearly don’t work, and I am pretty sure it has to do with the execution model of Google App Engine and so the only way to get it working right would be to delve into the internals of the SDK to fix
Got the major admin page for my app moving significantly forward. There are 3 “control table” models that provide the inventory in this application, and there’s what I hope is a nice AJAX-y admin page from which I want users to be able to manage those lists. First of 3 lists is done, so you can add and remove items. Made good progress on the second list supporting add and remove

Issues

Code is not in a completely stable state: second list’s table for add/remove is not adding quite correctly yet. That will be tomorrow’s work. I should probably put a bit of effort into understanding more about how to debug Google App Engine SDK by either getting it in an interpreter/debugger where I can see breakpoints, or learning how to do printf/stderr/console type logging in it. I am sure it can be done, and answer is probably a google search away. But I’m making progress without it, so it is not the biggest issue.

100x100 Challenge: January 28, Prologue-25 lines

Jonathan Altman — Wed, 28 Jan 2009 23:56:00 +0000

So I decided to start blogging my experience the day after I started actually doing the 100×100 challenge. Therefore, I get the benefit of hindsight, especially since I ended up well short of the mark. However, I would have to say the prologue was still fruitful.

Accomplishments

Here’s the accomplishments for the day:

Automated mounting of the truecrypt drive I keep most of my data on on my laptop (I’ve had a laptop stolen, the idea somebody had my data even though I knew the thieves would wipe the drive bothered me more than I thought). 5 lines of code
Installed Google App Engine SDK on my new laptop. Since I last touched my Google App Engine app, I got a new laptop and still hadn’t put the SDK on it
Got gitosis running on my re-imaged Joyent Accelerator. I beta-tested their latest image so I’ve installed it about 6 times now: I’m fast at it, but it still needed to be done. 5 lines of code
git clone-ed the repository from my home server to the Joyent Accelerator and to the new laptop
Installed KomodoEdit and NetBeans 6.5 with jvi and python environment. Decided to try NetBeans as my programming environment
Got past the roadblock that arose over 6 months ago when I put this app aside! 15 lines of code

Issues

Not too many really. I should probably figure out how to run Google App Engine in the NetBeans debugger.

Thoughts

NetBeans is pretty good. The python environment works fairly well. Like I said, it would be interesting to see if I can debug Google App Engine from inside it.

100x100 Challenge

Jonathan Altman — Wed, 28 Jan 2009 23:41:00 +0000

So I am going to set myself out a hopefully fun little challenge: 100 lines of code in 100 coding days. It’s my challenge (and if this catches on, my meme ;-)), so I get to define my groundrules. Of course, someone else who wants to quibble with these is free to come up with their own groundrules for their own challenge, publish them, and see how they do on their own ground rules. Point of this, however, isn’t to have a flame war on the ground rules. It’s to write code, have fun, and see where doing something this regimented leads.

Ground Rules

There will be 100 coding days. I am going to exclude certain days from the 100 day count like:
- Any day I’m away skiing
- Vacation by default, although if I feel like coding on a vacation day I reserve the right to make it a coding day
- Operational crises at work, although hopefully those are going to be at a comparative minimum these days
- Sick days, with the same caveat as vacation days
- One weekend day a week, choice of which one each week
For each of the 100 coding days, either:
- Write 100 lines of code
- Remove 100 lines of code by refactoring
Lines of code are counted as any non-comment, non-blank code that has any alphanumeric symbol, constant, value, etc. Here are some things I will or wll not count as a line of code:
- Do not count: comments
- Do not count: blank lines (zero or more whitespace characters)
- Do not count: closing lexical scope symbols like } in C/C++/Ruby etc
- Count: closing HTML/XML tags. They have identifiers on them, so I’m counting them. And remember, these are my rules
Blog about each day’s experience: how many lines, what was accomplished, what issues were resolved or came up; any other thoughts about the day’s effort
Publish the code: put the code out there for people to see at some point when it gets done. I will probably use my github account

Why I Am Doing It

I have a whole pile of interesting hobby projects that have been sitting around, not getting very far. There is some tangential work application to some of them, but some of them are just brain stretchers: play with something new, learn it, figure out some paradigms and programming models.

I am tired of not forcing myself past roadblocks in these hobby projects and letting them just languish. So this is a way to force myself to work on finishing at least one of them up. It is also an experiment in writing things that are just good enough. By pushing to finish them, I am hoping I won’t get into bouts of perfectionism of making sure every single artifact in my code utilizes the cleanest, most elegant paradigm in the toolkit I’m working on, since a major part of the goal of this is intellectual mastery of the subject matter. Going back to refactor, I may clean things up and make them more elegant. But this may force me to get things done instead of polish them to perfection. If I want to clean something up, I’ll go back and do it after I’m done with a first cut.

What Am I Coding?

I have been playing with a Google App Engine application since right after their initial limited beta got expanded the first time and I got my invite. The app has been sitting stuck on a particular error for over 6 months now. So I am going to finish the application.

One goal with the app, besides learning Google App Engine, is to build myself a modern, ajax-y web application using new shiny toolkits on the server and browser. As of right now I am using Google App Engine on the back end, and YUI for the DHTML/Ajax stuff.

I may post more about the actual experiences with the toolkits as additional posts when there is a longer topic. DHTML toolkits is a very possible start. YUI is definitely an “accomodation” choice: there are reasons I’m using it here that are very specific to this project’s situation that I’d like to explore.

After Google App Engine?

Another goal is to play with “cloud”-type apps. That was the interest in Google App Engine when it came out. Given that, if I actually finish the Google App Engine app, some other things I’d like to attack would be to see what challenges I face trying to port the app to different platforms, for example:

Heroku, where I also have a beta account languishing
A different python framework like TurboGears2 or Django, running on my Joyent Accelerator and maybe even Amazon EC2
The Nitrogen Erlang framework, again hosted on my Joyent Accelerator or Amazon EC2 (or both!)

There has been lots of discussion about portability, vendor lock-in, OSGi stack-level mismatches between various cloud offerings. By taking a sample app that is small enough to be written reasonably easily, but has enough breadth of functionality to tickle enough parts of a modern AJAX web app, maybe I’ll provide some interesting data points about writing for the cloud.

The Mainstream realizes SOA is going the way of WS-*

Jonathan Altman — Mon, 11 Aug 2008 19:21:00 +0000

So I disagree with the way the argument in this post is framed, but I am glad to see the “mainstream” tech press realizing there’s a better way to get to SOA:

A growing number of companies are finding that lower-visibility Web-oriented architecture (WOA) developments, spawned through grassroots movements, are a better route to the service-oriented architecture. WOA, like SOA, is an architectural approach to system design, though WOA is resource-oriented rather than service-oriented. What’s the difference? While the core SOA design unit is a reusable service that fulfills a distinct business function, resource-oriented services are more limited and data-focused.

SOA and WOA work at different layers of abstraction. SOA is a system-level architectural style that tries to implement new business capabilities so that they can be consumed by many applications. WOA is an interface-level architectural style that focuses on the means by which these service capabilities are exposed to consumers. Governance, quality of service, security, and management are of equal importance, whether the functionality is being delivered via SOA or WOA.

I think the delineation between SOA design units as a service fulfilling a distinct business function and WOA as a resource-oriented service being more limited and data-focused is so much dissembling for SOA being an attempt to force a top-down, waterfall-based model on what services you offer in your architecture versus an iterative or even agile strategy of building the individual services and then gluing them together.

I think SOA was also overblown in the framework for tying them together, which is the root of this problem, and leads to the conclusion I made up above. Put a bunch of webservices out there that handle orthogonal responsibilities, make it easy to access them (personally, preferably with easy HTTP/POX or a light SOAP layer), rather than a huge management stack that services have to a priori fit into, with the up-front design and overhead that comes with it.

Good point about any Web Services != RPC

Jonathan Altman — Fri, 25 Jul 2008 15:44:34 +0000

So ordinarily, this post would have gone up as a link in del.icio.us, but the interesting part of it is actually a single quote that flows in the article but is not the main point. So I will just crib the interesting part here. It is worth reading the entire post as it is interesting, but what I want to call out is:

bq.IMO the real underlying problem is that as long as programmers expect to write a class and flip a switch to get a service or one or more RESTful resources then we have nothing really but RPC masquerading as something else. Both resource and service advocates would be well-off in trying to move the developer community to get past the “class is all I need” stage. If REST is successful in getting developers to get their hands dirty more power to it.

...And we shall call it NetBlub

Jonathan Altman — Wed, 02 Jul 2008 06:07:00 +0000

Paul Graham first wrote about a strawman hypothetical programming language blub that examined the constraints that people who choose to stay firmly embedded in only one language seem to impose upon themselves and their programming capabilities and creativity.

Steve Vinoski, who has been writing a bunch about some of the failures of RPC-style distributed systems technologies (and should know, having been involved in CORBA), I think just extended the theme to distributed systems programming here.

Running Rails Apps on a Nokia N810

Jonathan Altman — Wed, 13 Feb 2008 05:28:00 +0000

Goaded on by requests for screenshots of Tracks running on my n810, I decided to instead document to the best of my recollection what I did to get Tracks and Instiki running on my n810.

1. Preface: Why?

2. Screenshots

3. Prerequisites

4. Tracks and Instiki

5. Wrapping Up

DISCLAIMER: I am going to show you how to do some things that can probably badly mess up your device if you get them wrong, and maybe even if you follow these instructions to the letter. I do not promise that these instructions are even complete or accurate anymore; I am nearly positive the instructions below are incomplete regarding what to install. You follow these instructions at your OWN RISK. This worked for me, it may or may not work for you, with or without additional steps. I did this about 3 months ago and was not taking good notes because I figured over time apt packages would catch up and this would not be necessary to repeat. If you follow and you get warnings you need to install additional stuff to continue, you should probably assume that is correct.

Preface: Why?

So one of the main reasons I actually got a Nokia n810 internet table (Linux/gnome-based tablet) was because:

It had a keyboard
It ran Linux and was reasonably powerful enough to possibly run some interesting things
It might let me replace my horrible system of “engineering notebook” plus wiki on my personal laptop plus complete lack of organizational system for keeping track of tasks with a single device that could provide all of that in a small, portable package

To get this, however, I was going to have to be able to install 2 Rails apps that I liked:

Instiki, for wiki
Tracks, for GTD (Getting Things Done) task management

I pre-ordered my n810 directly from Nokia (with a very nice discount) before it was available, and received mine I think within the first week of its being generally available in the United States. So to preface this description of how I got things working, I did all this in late November, 2007. Some packages may have moved around, and there may be better ways to do things than what I had to do. But Chinook (OS2008) ported packages were fairly slim at that time.

I should also point out that I was not interested in developing Rails apps on this machine, just installing and using them. Once I got things to an acceptable level of “done” for me, I did not investigate some pecularities further. So some things that you will not have after this are:

The ruby gem system is not installed. I did get it installed, but could not get it to actually read the gem catalog, so I see no reason to describe how to install it. Could it be made to work? Don’t know and I don’t care for my purposes on this box. I have gem working lots of other places on different chip architectures, but the n810 was not a target I needed it working on at this time
I did absolutely no investigation on how to have Rails apps start when you boot up the n810. I have a shell script I use to start my apps, and anybody who wants to take that to the next level and get this autostarted, please document it and I will gladly use it. But my shell script works for me since I reboot the thing maybe once every 3 weeks
This does not get you the Rails gem installed anywhere in your site_ruby, nor ActiveRecord, nor anything else. Most packaged Rails apps seem to freeze their Rails install into railsapp/vendor anyway these days, so installing a pre-packaged app works just fine. So my instructions may not work for some Rails apps, and it certainly won’t work for you to start making your own new Rails app on your n810

Screenshots

So without further ado, as a tease, here are screenshots of Tracks running on my n810. As you can see by the lateness of many actions, I have been better about getting Tracks set up than in actually having it improve my personal organization!

”

The Tracks “Home” view. David Allen would be appalled!

Adding an action. Notice that the Ajax calendar works just fine.

Prerequisites

These are the steps to take to get the basics set up on your n810 to even put a Rails app like Tracks or Instiki on it.

Turn on Red Pill Mode

I am not sure this is strictly necessary, but I had it on while I was doing this,and I suspect it’s necessary. This is the first but not the last dangerous part of these instructions. Instructions on doing so, and what it does for you, are on the Maemo wiki here

Libsqlite3-0

libsqlite3-0 appears to already be installed, so there is nothing to do. But you might want to confirm in the Application manager that it is already installed.

Install Ruby and Ruby Sqlite3 Bindings

~~-I got the packages from http://maemo.rubyx.co.uk/ruby-maemo/ however the site appears to have been down for a while now.~~- The ruby packages I installed appear to now live at http://gplsystems.com/apt/dists/chinook/main/binary-armel/Packages (thank you friend and coworker who wishes to remain anonymous). The packages I installed, which I recall all coming from there, were:

libruby1.8
libruby1.8-dev (not sure it’s necessary, but I grabbed it)
ruby1.8 (1.8.6-p110-1)
ruby1.8-libxml (I don’t think it’s necessary, but I do a lot of stuff with XML)
ruby1.8-maemo (again, not sure it’s necessary)
ruby1.8-sdl (nearly positive I did not need this)
ruby1.8-sqlite3 – definitely required

I found and installed rubygems from somewhere, but I could never get it to do anything but hang trying to update catalog. Both Instiki and Tracks releases ship “complete” so there’s no gems needed, so I skipped this.

Add the Maemo Repository to Application Manager

Add the maemo stable repository at http://repository.maemo.org/. When you are done, the apt.sources line ends up looking like “deb http://repository.maemo.org/ chinook free non-free” for those of you that like to look at the raw apt package configuration files.

I also added the Maemo extras repository and maemo-hackers.org repository

Install p7Zip, gcc, make and some needed Libs

Since rubygems didn’t work for me, I decided to install mongrel from source. You need gcc, and I think make. You also need something to unpack tar/zip archives, and at the time the only maemo package I could find was p7zip. These are in the maemo repository/repositories you added earlier. I have

p7zip 4.42.maemo-1
make 3.80-9osso
gcc 3.4.4
libc6-dev if you don’t already have it

There may have been some other pieces needed too.

Download and Install Mongrel

Webrick runs on the n810, for values of run equal to a geriatric snail. You will not be happy with a Rails app running under webrick. Mongrel is, while not exactly instantaneous, at least responsive enough to run an AJAX-y Rails app.

Download the mongrel source tarball from http://mongrel.rubyforge.org/. 1.1.1 was the latest at the time but they are on 1.1.3 as of February 5, 2008. Untar to a directory (using p7zip). Then do ruby setup.rb which should configure, build, and install mongrel. You should now have /usr/bin/mongrel_rails.

Tracks and Instiki

Where to Install

You will be installing Tracks and Instiki from source tarballs or zipfiles. After you download them, you will need to unpack them somewhere, using p7zip. I put them on my removable media card, which is /media/mmc1 because I was concerned about the GPS/mapping software filling up the fixed 2GB memory card /media/mmc2. If you plan to swap out memory cards often that might be a bad decision for you, but I am happy with it.

Tracks

Download a Tracks tarball/zipfile. I used Tracks 1.043 which was the latest “release” drop on their site, but I am sure you could grab trunk out of the Tracks source repository and turn that into a tarball too
Untar/unzip the source archive and cd to the top directory of Tracks. In my case that was /media/mmc1/tracks-1.043. You may lay it down differently, but if so remember to alter your paths throughout the rest of these instructions appropriately.
cd into the tracks directory you just unpacked
Make sure that the database.yml in the config subdir is set up the way you like. I left mine using db/filename.db as it shipped
Now the moment of truth: start up Tracks. From the main directory you could do ruby script/server just to test (it might start up webrick instead of mongrel, for values of might equal to probably). If it starts up without error, point your web browser at your Tracks instance: http://localhost:3000/
Once you have it up and running, you can stop Tracks with ctrl-c
Now try mongrel. /usr/bin/ruby /usr/bin/mongrel_rails start -c /media/mmc1/tracks-1.043 -e production -a 127.0.0.1 -p 3000 is what I use in my environment. You might need to adjust the path after -c to match how you laid down Tracks. It should start up, and you should be able to point your web browser at it. If so, go ahead and stop Tracks by typing ctrl-c.

Congratulations, you’ve installed Tracks on your n810!

Instiki

Download Instiki 0.12.0 (or newer if it exists and you want it). I would avoid earlier versions of Instiki that use Madeleine for persistence. 0.12.0 uses sqlite3 for persistence, and that seems safer than using Madeleine on the n810
Untar the source archive and cd to the top directory of Tracks. In my case that was /media/mmc1/instiki-0.12.0. You may lay it down differently, but if so remember to alter your paths throughout the rest of these instructions appropriately.
cd into the instiki directory you just unpacked
Make sure that the database.yml in the config subdir is set up the way you like. I left mine using db/filename.db as it shipped
Now the moment of truth: start up Instiki. From the main directory you could do ruby script/server just to test (it might start up webrick instead of mongrel, for values of might equal to probably). If it starts up without error, point your web browser at your Instiki instance: http://localhost:2500/
Once you have it up and running, you can stop Tracks with ctrl-c
Now try mongrel. /usr/bin/ruby /usr/bin/mongrel_rails start -c /media/mmc1/instiki-0.12.0 -e production -a 127.0.0.1 -p 2500 is what I use in my environment. You might need to adjust the path after -c to match how you laid down Instiki. It should start up, and you should be able to point your web browser at it. If so, go ahead and stop Instiki by typing ctrl-c.

Congratulations, you have installed Instiki on your n810.

Wrapping Up

Now that you have Tracks and/or Instiki up and running, what next? I left my apps running on their default ports of 3000 and 2500, but you could run them on different ports if you chose. I saw no reason to do that, nor to find a webserver to proxy them to so they are off the “main” webserver. That’s just overhead the n810 really does not need.

Starting up Rails Apps

Once I was happy with my install, I made myself a little shell script to fire them both off. When I boot up, I start up an XTerm and fire off the script. Here are its contents (sorry for the iframe, it was easier):

Stopping Rails Apps

The easiest way I stop both my apps if I need to, like if I want to hook up the USB cable or otherwise want to make sure the Rails apps shut down cleanly, I just issue a killall ruby and that kills the mongrel processes given how I start them. Before you just do that, make sure you know what ruby processes are running on your n810 and that you’re ok to kill them all.

Note that it can take a good few seconds, from 15-20 up to maybe 30, for all the Rails apps to respond to the kill signal. Just be patient. I also highly recommend aliasing ps -ef | grep in the shell to pgrep because inputting the pipe symbol on an n810 is fairly cumbersome.

Switch (back)

Jonathan Altman — Sun, 25 Nov 2007 19:20:00 +0000

Well, after 12 years I have switched (back) to Macs.

My first computer was an original 128k Mac, one of the very first ones. My mouse actually had a 5-digit serial number, IIRC. I gave up in 1995 swearing I would never buy another Mac:

I bought a Powerbook Duo 210-possibly the worst Mac ever engineered- right when it came out, shortly before Steve Jobs cut the price in half, and then shortly after that discontinued it. And no, he didn’t give me any funny money to go spend in his stores after he did it
The various unixes, which is how I made my living at the time, all had reasonable PC-based implementations that were free and open source. Linux was viable, and FreeBSD 2.2 was a really nice, stable OS
The Mac just did not have interesting software that I wanted to play with, and I could run systems I could get paid to play with on x86 pc hardware
Oh yeah, did I mention the turd of a computer that the Powerbook Duo 210 was?

The Good

So why the switch back? It comes down to things Just Working. I’ve been using various Linux distros, most recently Ubuntu, at home for a while. I will continue to run Ubuntu on my home laptop. But for a computer for the rest of the family to use, and for certain things for me, the Mac is just easier:

It is just about as easy to manage software on the Mac as on Ubuntu. I am convinced that the debian apt system (or possibly similar like yum or rpms) are the way to go for maintaining systems. But Apple’s installation system has so far been very easy to work with to get things on here.

Most importantly, once software and drivers are installed, the hardware and software Just Works

As a quick example, I installed the iSync plugin for my Nokia N95. I then used the iMac’s bluetooth wizard to connect to the phone, it found it and paired properly (no extra credit, most things do these days), but then iSync popped up and within 10 minutes of starting I had downloaded the plugin, installed it, connected my phone, and synced my phone into iCal and the address book

*Unix-y goodness. I like being able to pop into a shell and do things, and having rsync and friends around is nice

The Bad

So everybody touts the awesome OSX GUI. But here’s the deal, much of it is still the best that 1983 has to offer.

The single menu bar at the top of the screen that switches as you change apps has got to go. I have had the computer running less than a day and I’ve already thought I’ve closed an app about 20 times only to remember that closing the last window…closes the last window. It is too hard to get into and out of apps
I’m not thrilled about the dock showing both open and available apps. I would prefer one list of open apps and another of apps I frequently use to click on. I know there is a visual indicator of what’s open or not, but my dock is cluttered because I am used to using a strip of icons for apps I start frequently

Overall

Overall, I am happy with the switch back, but I think I’m jaded enough not to become too much of an Apple fan boy. There are too many usability nits left in the OS from 20 years ago.

I’m using firefox and thunderbird for mail because at the base of it I want an OS to run my apps on top off, and I like that I have the same apps on Windows, linux, and OSX.

Finally, I am sure I have said something in here to anger Mac, Windows, and Linux/Debian/Ubuntu fans everywhere. Remember, this is my choice. I use all 3 OSes now every day (Windows at work, Ubuntu on my personal machine, and OSX on the family computer). I use what works for me out of each of them, and none of them does exactly what I want for every single thing. Linux->Debian->Ubuntu and OSX each have their strong points, and I like each for what they can do. But each has downsides too. Remember, this is all IMHO, with the emphasis on my and opinion. You are free to have yours, and have them not be the same as mine.

Initial Lockdown of a Joyent Accelerator

Jonathan Altman — Fri, 25 May 2007 04:37:00 +0000

Here are some quick steps I did to do initial lockdown of a freshly created Joyent Accelerator:

Change passwords

Sign in as admin via secure shell to the default account, change its password
su to root and change the root password
Go into virtualmin->webmin->Webmin Users->Click on the admin user. Then set Password Authentication to Unix Authentication in the dropdown box, like in this screenshot: Hit the Save button at the bottom of the page. After you do this, you will have to log back in to webmin. Alternately, you could just set the password to be the same as the one you used for the admin user you secure shell’ed in, if you are worried about webmin having access to the Solaris password authentication system. But then you also have to worry about keeping the passwords in sync.

Shut off unnecessary services

Disable apache: I am not ready to run a webserver yet, so I shut off apache by su’ing to root and running # svcadm disable cswapache2
Make postfix only accept mail from localhost: Webmin->Server->Postfix Configuration->General. Set the text box on “Network interfaces for receiving mail” to localhost, like in this image: then save. Then stop and restart postfix

When I was done, my netstat -a -f inet display showed only the following listening ports:

*.s s h: s s h daemon
*.10000: webmin
localhost.smtp: smtp, but can only be accessed via localhost
localhost.3306: mysql daemon

Jonathan's Pancheria: Category technical

100x100 Challenge: January 30, Day 2-150 lines

Summary

Accomplishments

Issues

100x100 Challenge: January 29, Day 1-119 lines

Summary

Accomplishments

Issues

100x100 Challenge: January 28, Prologue-25 lines

Accomplishments

Issues

Thoughts

100x100 Challenge

Ground Rules

Why I Am Doing It

What Am I Coding?

After Google App Engine?

The Mainstream realizes SOA is going the way of WS-*

Good point about *any* Web Services != RPC

...And we shall call it NetBlub

Running Rails Apps on a Nokia N810

Table of Contents

1. Preface: Why?

2. Screenshots

3. Prerequisites

4. Tracks and Instiki

5. Wrapping Up

Preface: Why?

Screenshots

The Tracks “Home” view. David Allen would be appalled!

Adding an action. Notice that the Ajax calendar works just fine.

Prerequisites

Turn on Red Pill Mode

Libsqlite3-0

Install Ruby and Ruby Sqlite3 Bindings

Add the Maemo Repository to Application Manager

Install p7Zip, gcc, make and some needed Libs

Download and Install Mongrel

Tracks and Instiki

Where to Install

Tracks

Instiki

Wrapping Up

Starting up Rails Apps

Stopping Rails Apps

Switch (back)

The Good

The Bad

Overall

Initial Lockdown of a Joyent Accelerator

Change passwords

Shut off unnecessary services

Good point about any Web Services != RPC