I’ve compiled Debian 3.8 for the Beaglebone Black (from the RCN git repository) and have it running on an SD card. My Beaglebone Black has an active Ethernet connection. I opened a Firefox connection to the BBB from my PC (running Ubuntu). The connection is successful but with the following message-
It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet.
I would like to clone the BBB webserver setup as well as find and install copies of the Node.js and Cloud 9 IDE that are pre-compiled and shipped with the Beaglebone Black if they exist for Debian.
Did I miss something during the build or do I get what I need from a different Beaglebone Black git repository someone else is maintaining?
Add this repo, which includes a backported nodejs with npm included:
asc key:
https://raw.githubusercontent.com/beagleboard/image-builder/master/target/keyring/debian.beagleboard.org-archive-keyring.asc
sudo apt-key add debian.beagleboard.org-archive-keyring.asc
Then add too: /etc/apt/sources.list
deb http://debian.beagleboard.org/packages wheezy-bbb main
deb-src http://debian.beagleboard.org/packages wheezy-bbb main
sudo apt-get update
sudo apt-get install nodejs nodejs-legacy npm
cloud9 is installed here:
https://github.com/beagleboard/image-builder/blob/master/target/chroot/beagleboard.org.sh#L223
Regards,
Which version of Node.js is the Debian image using that does not include npm ? I’ve never used the prebuilt Debian image but have built my own, and compile node.js from source ( also not the absolute latest ) but apparently new enough to include npm. I want to say 0.10.6 but I’d have to find and read my notes to be sure.
Hmm, odd. I followed the “how to from source” instructions from the git repo for Node, and it mentions that npm is now part of the Node.js build now. When I did get a workign build, sure enough npm was already installed. Those instructions as is did not work, but was very close( required some MAKE switch for ARM I’d have to read my notes to remember ). Oddly enough I found information on this switch from armhf’s dated instructions . . . worked like a charm.
before we had a *.deb package on debian.beagleboard.org this how i was
building it:
--without-snapshot --shared-cares --shared-openssl --shared-zlib
--prefix=${node_prefix}
https://github.com/beagleboard/image-builder/blob/bb.org-v2014.02.18/target/chroot/beagleboard.org.sh#L33
Regards,
The instructions I noted were as follows . . .
apt-get install python build-essential
mkdir /nodejs
cd /nodejs
wget http://nodejs.org/dist/v0.10.15/node-v0.10.15.tar.gz
tar xzvf node-v0.10.15.tar.gz
cd node-v0.10.15
./configure --without-snapshot
make
./node -e ‘console.log(“Testing . . .”);’
make install
node -v
npm -v
The bold line being the command needed to build for ARM. Also this is where having a rootfs on an NFS share comes in handy. As the very latest version failed to build correctly but somehow managed to install. So, not knowing much of how Node is installed, and instead of hoping I find all the crap that needs removing. I just revert from a pre-existing backup ( tar the whole rootfs directory on the server prior). This way I can experiment with newer versions and just revert when it doesn’t work out.
Maybe I should write another blogpost on how I personally think such a dev system needs to be setup . . . I dont know. It seems as though it would save a lot of grief for Debian + BBB newbs.