Cloud 9 IDE on Intel Edison

Introduction: Cloud 9 IDE on Intel Edison

In this Instructable, we are going to install Cloud 9 IDE onto the Edison.

Using Cloud9 IDE will allow you to write (and debug javascript) applications right from your browser.

We will be setting up the Cloud 9 IDE server on the Edison.

What this would mean is, the software required to start developing with Intel Edison is minimal. All you need is serial emulator software to setup the environment and a browser to start developing.

Step 1: Preparing the Edison

The preparation process involves downloading and compiling many packages which can easily take up the allocated space for the root file system on eMMC of the Edison.

So you'll have to boot from the SD card to complete this process.

You can refer to this topic or this blog post on instructions for preparing the SD card.

I've used 8 GB SD card successfully in my tests.

Once you have booted up the Edison from the SD card, head over to next step.

Gain access to Linux console either through serial connection or SSH.

Step 2: Installing the Cloud 9 IDE

We need to update the repo list on the Edison (if you have already not done that).

Start 'vi' editor to edit the file /etc/opkg/base-feeds.conf

vi /etc/opkg/base-feeds.conf

and press key 'i'

Copy the following lines:

src/gz all
src/gz edison
src/gz core2-32

and paste it in the console with 'vi' still running and edit mode enabled via the 'i' command.

Press 'esc' key followed by ':wq' to save the changes and exit.

Install git using following set of commands:

opkg update 
opkg install git

Get the script for preparing the Edison for installation of the Cloud 9 IDE

git clone c9
cd c9

Start the installation process with the following command:

sh install

This process will take some time (about ~3-4 hrs)

During the installation you'll be prompted to answer if you wish to install a version of "ps" program that is required by the Cloud 9 IDE, enter 'Y' and proceed.

Once done with installation, you can start the Cloud 9 server using following command:


You can make this command run automatically using the cron program.

If you are interested in knowing the working of the above mentioned script, you can have a look at this post.

Step 3: Using the Cloud 9 IDE

Note down the IP address printed out when you executed the last command in the previous step and enter the entire string following "http://" including 8080 into the navigation bar of your browser.

You should see Cloud 9 banner in your browser and a after a few moments the application should be loaded.

Create a new file using "File->New File" and save the file with "File->save as" while saving the file you will have the opportunity to specify the programming language that you will be using to develop your application vis the extension.

If you were to write your application in c, the extension would be '.c' for Python, it would be '.py' for javascript, it would be '.js' and etc... This process would select the required runner.

You run the application using the "run" button in the tool bar. To stop a script, click on the "stop" with big red square button.

You can also use the "Terminal feature"(Alt-T for new terminal) to gain access to the Linux console on your Edison within the IDE.

If you are interested in developing applications for the javascript on Edison, you can debug your application in Cloud 9 IDE. Insert the break point by clicking on the left of the line number display and click on run to start debugging.

The script sets the workspace location as "/home/root/c9wks" as the default location. You will find all the scripts and applications that you have written in this folder.

You can configure the workspace path, the path where the file
created within the IDE (or outside) will be stored and this will be the root directory for the file list window on the left of IDE by modifying the variable "WKS". You can also set user name and password by specifying non empty string (within "") as values for USR_NAME and PASWD respectively. You will be prompted to enter these credentials when you access the cloud 9 server. You can find all these variables at the very top of the file "". You can use vi to edit these parameters.

If you are interested in learning more features of Cloud 9 IDE, you can refer to official documentation here.

Be the First to Share


    • Rice & Grains Challenge

      Rice & Grains Challenge
    • CNC and 3D Printing Contest

      CNC and 3D Printing Contest
    • Lamps Challenge

      Lamps Challenge



    7 years ago on Introduction

    I've added instructions (in the last step) for enabling basic authentication when using the supplied script. Enabling this causes cloud 9 IDE to prompt you to enter the credentials to access the IDE interface.


    6 years ago

    Just Incredible


    Reply 6 years ago

    Yes it should be. I have made the change.
    Thanks for brining it to my notice.


    7 years ago

    Incredibly Great......


    7 years ago on Introduction

    A suggestion: having cron to start automatically seems not cool. Since Edison OS uses systemd then maybe a better solution is create a systemd service definition.

    A question: how much disk space is required? I don't want to use a SD card and I have 1.3GB free on my /home so maybe I can run without an SD card anyway.


    Reply 7 years ago on Introduction

    Yeah I too believe systemd is a nicer solution but I feel that it is more complicated to use compared to cron. The configuration required is some what overwhelming and the more important point is, I do not want to mess with user's Linux installation (I think I'll keep that only to the software for now :)). Maybe next time I'll give it shot.

    I am assuming you are talking of eMMC. The 1.3GIG is allocated to home alone and not the root file system and you can not resize it when it is running.

    While running the make with install, for node itself, root would run out of space while trying to copy executables and supporting files to bin. Do a df -h with eMMC boot image to get an idea of this situation. When I started out, I had fresh Edison image and soon ran to this problem and had to boot from external storage to get around this issue.