RaspNXT - a standalone NXT environment for the Raspberry PiUPDATE 2014-01-08: NXT 0.5.3 coming soonUPDATE 2014-01-05: NXT 0.5.0
cancelledUPDATE 2014-01-02: NXT 0.4.8, update script, blockchain-less
This package contains the
current stable version of the NXT server and the
Embedded Version of Oracle JRE that you can
run on your Raspberry Pi as-is. You can get it
from my public node server (hash checksums coming soon). This archive contains most of what you might need, including some helpful utilities and scripts.
If you have the JRE already or insist on using another one,
try this archive. Both links always link to the newest version of the package. You can get older versions or other stuff
from the nxt root of the server.
Notice: Unlike the initial version, there are no block files in this version of the package. This reflects the makeup of the main NXT releases, which are now also blockchain-less. If you would rather use a basic blockchain to update from, but don't have one yet, you can
download one of these.
To download and run it on the Pi, do the following steps in a local or remote console. I assume you have the Pi up and running already, using e.g. Raspbian. I myself am using Raspbian, however, the package should also work with other distributions.
wget http://109.230.224.65/~nxt/nxt_rasppi.tar.gz
tar -xpf nxt_rasppi.tar.gz
chown -R *youruser*:*yourgroup* nxt/
cd nxt
ln -fs webapps/root/WEB-INF/web.xml configfile
./run_nxt.sh
I now have incorporated my
public node update script into the package. Called automatically by the run script before starting the JVM, it fetches a list of well-known public nodes and puts them in your config.
You can tweak the JRE call in the run_nxt.sh script if you want. After some testing with the new version, I have found that not that much memory is needed.
Also, I put a symlink in the rootdir called configfile which leads to the web.xml file, for easier access.
I recommend running the server in some sort of backgrounding context, as it is basically a daemon. Use a multiplexer like screen or at least use nohup. For a more comprehensive guide on setting this up, I recommend
this how-to which also references this package.
If you want to access the client from another machine - which you probably do want when starting the server or using the Pi as a whole remotely - remember to put your accessing IP or the "*" wildcard (no quotes) as allowed addresses in the configfile.
Have fun with it, and feel free to post some impressions of RaspNXT on your RPi
