Justin Latimer


Cloud9 Workspace Disk Quota

I've been working on a new project on the bus, using the new Cloud9 IDE. It's in C++ using boost. I'm experimenting with using GYP to build boost and using a git submodule to include a specific version of boost from the boost github superproject.

So far this approach is working well, but there is one problem: the history of the boost superproject is quite large. I was getting pretty close to the disk space limit of my Cloud9 workspace (1.5GB quota, 32MB remaining), and was getting a little red warning banner at the top of the screen every time I loaded it. But yesterday when I loaded my workspace, I got a migrating screen. When it finished, I didn't get a warning.

Sure enough, when I checked quota -s the results were as below:

Size  Used Avail  Use%
4.7G  1.4G  3.2G   30%

I checked and I couldn't find any announcements about increased disk space, so I'm not sure what the deal is, but I'm certainly not complaining! Thanks Cloud9!


New Cloud9 Launches

The new Cloud9 IDE which I had previously blogged about is now live! I participated as a user in the public beta and found they had really taken it to the next level.

As a developer, there was a gem in the release announcement - the new Cloud9 IDE is built on Docker! Docker has been on my list of things to get up to speed on for a while. It looks like Docker is becoming the default building block and enabling a whole suite of applications that previously wouldn't have been possible because of the ops nightmare. Seriously, Cloud9 give you an Ubuntu backed browser based IDE, with sudo access. Before something like Docker building something like this securely would be next to impossible.

I can't wait to see what other previously out of reach business ideas Docker enables, and I'd love to hear from Cloud9 about their experiences building with it!


New Cloud9 IDE

I've used Cloud9 IDE for a few years now, for as much development as I can. In some ways it's not as powerful or customizable as using a native environment, but the tradeoff is worth it: you can sit down at any computer with a browser and an internet connection and be back where you left off, literally in seconds. I use Cloud9 to author this blog.

For personal projects, I mostly use node.js, which has fantastic support on Cloud9. You can do debugging, breakpoints, live variable inspection, etc. All the things I've never been able to set up in my local development environment using Sublime or whatever. So in that respect Cloud9 is actually ahead! One of my projects is node-midi, a native node.js module for MIDI i/o. I haven't been able to develop node-midi on Cloud9 because although it has a C++ compiler built in (this is actually amazing when you think about it!), node-midi requires ALSA to be installed to compile successfully on Linux. So I was out of luck - until now.

Cloud9 have released a new beta, where every workspace is backed by an Ubuntu VM, and you have sudo. I was lucky enough to get access to the beta (which was pretty easy - I just asked) and once I setup a new workspace for node-midi I did a sudo apt-get install libasound2-dev and then successfully compiled node-midi.

The new Cloud9 beta is amazing and not just for that reason. The new Terminal is much more stable - I do most of my development on a Chromebook over 3G tethered to my iPhone, and had occasional terminal weirdness which i haven't seen in the new beta.

Now the only thing it can't do is actually run the tests for node-midi. This may be possible because in theory with sudo access I might be able to actually set up enough of ALSA to use the virtual MIDI ports, but I haven't been able to make it happen. That would be mind blowing.