Skip to main content

Developing Sproutcore apps on

The Cloud9 online IDE running on Chrome/Mac.
Today I was looking for a way to quickly edit a pull request to the Sproutcore project without booting up my laptop, but using the MacMini in the living room instead, which is always on, being our main entertainment system.

Turns out it's quite easy if you do not mind signing in into another online service: the Cloud9 online IDE.

Cloud9 can sign you in with your GitHub credentials, so I signed in, selected my sproutcore fork from the project list, cloned it and, presto, I was ready to do some programming.

In addition to loading a complete web-based IDE, Cloud9 also boots up a virtual machine from RedHat's PAAS OpenShift to host a very cool web-based command line. The CLI can be used to run git commands but can also be used to run (almost) any command you like.

The virtual machines for free accounts are automatically suspended when not used for more than 15 days, which means that the next time you sign in you will still find your environment, but you also will have to wait a little while the VM wakes up again. Paid accounts VMs are never suspended and are always running.

Anyways, going back to my pull request, I quickly added a unit test for the new behavior. I also wanted to try and run the unit test, but as you might know, to run any Sproutcore app in development you first have to launch their Ruby-based server which takes care of assembling the app, delivering it to the browser and also proxying requests to any remote backends.

To run the server, which is called sc-server btw, you first have to install the ruby gem called sproutcore.
So on the command line I typed the following commands:

# ruby -v
ruby 1.9.3p448 (2013-06-27) [x86_64-linux]  

to check the ruby version. Sproutcore requires 1.9.x, so we are good to go. Then simply:

gem install sproutcore
sc-server --host $IP --port $PORT --allow-from-ips='*.*.*.*'

to install the gem and its dependencies and the run the server.
The HOST and IP variables are set for you by C9 especially for the purpose of running network daemons (like a database, a node server, etc) that can be accessed externally.

After sc-server has started, to access the Sproutcore server you simply have to point your browser to:

which in may case was:

Happy hacking!

Popular posts from this blog

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post.
Btw: the recovery, depending on db size and disk speed, is going to take long.

The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux.

The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking.

Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd into the mirth home. …

NGINX stream module with dynamic upstreams

NGINX has had support for dynamic upstream modules for a while in the community distribution and examples abund. I think this is probably one of the clearest I could find.

Finding a similar config for stream proxies turned out to be surprisingly hard, so here I'm sharing my solution in the hope that it can be useful to somebody. Or someone more experienced can point out a better alternative.
In my case my upstream is an ELB which can and will change ip address often so using the static DNS name was not an option.