Installing Persevere

Persevere is not a single monolithic web server like Apache. Rather, it’s a set of server apps – or JSGI middleware – working together. While this is very powerful in terms of flexibility and extensibility, it complicates the installation process. Installing Persevere has become much easier with tools such as Nodules, however, the whole process might still not be for the faint-hearted.

Persevere Logo

Deciding on a server engine

The first decision you have to make is which server engine to base your Persevere instance on. Two options exist:

node.js is a JavaScript-interpreter written in C/C++, which makes is very fast and light-weight. It is based on Google’s V8 JS-engine, which also powers the Chrome web browser. node.js has a completely new take on concurrency. There are virtually no synchronous (blocking) operations – everything is asynchronous – which makes it excel at concurrency, i.e. providing a very good foundation for a web server.

Rhino is a JavaScript-interpreter written in Java. While it is usually second to node.js in terms of performance, it has been around for a longer time. Rhino’s codebase is well tested, stable and much less likely to undergo larger structural changes compared to node.js. Rhino is sponsored by Mozilla and is easier to install since there are official binaries. Narwhal brings a CommonJS module/package system to Rhino. Theoretically Narwhal could be run on any JS-interpreter (including Node.js!), but support for Rhino is the most complete.

Even though Persevere aims to be completely compatible with both node.js and narwhal/rhino, my impression is that it generally works best (fewer issues to troubleshoot) with node.js. This article will assume a node.js server engine.

Installing node.js

You can download the source code from and compile it yourself.

If you have a Mac, you can do it the easy way, by installing a pre-built binary package:

If you’re on Windows, you can compile it using Cygwin. As of quite recently, node.js offers binaries, but only for the unstable (development) versions.

Node.js should now be installed. You can verify this by opening a Terminal and run

node --version

Download nodules

Like stated above, Persevere consists of many individual components, which may in turn require many other dependencies. To avoid having to fetch them all manually, we use a sub-project of Persevere called nodules, which will automatically download all dependencies for us – on demand.

In fact, nodules also offers a remarkable feature – module hot-reloading. If you’re from a Java-background, you will immediately realize the benefits, but it might not be obvious if you’re from a PHP background (or any other interpreted platform). However, this greatly increases your efficiency when working with Persevere as it will auto-reload your source code when you save your files.

Download nodules from – or use this direct link

Unzip and save nodules in an easily accessible location – nothing needs to be installed.

Installing the Persevere application template

Download persevere-template from github for a bare-bone minimal Persevere application. The template is essentially empty, apart from the minimum amount of code needed to fire up a Persevere server instance. – or use this direct link

Now, using the Terminal, go to the template directory and start the Persevere template app.

cd <path-to-persevere-template>
node <path-to-nodules>/lib/nodules.js

You will see that nodules immediately starts to pull in all the required dependencies. The first time you do this, it might take a while, but don’t worry – all modules are cached (saved) in in your app’s subdirectory “downloaded-modules”.

Did it work?

If there were no errors, you have your very own Persevere app up and running. Verify this by pointing your browser to http://localhost:8080/. It should look something like this:
Screenshot of a standard Persevere directory listing

Persevere being a very dynamic project, odds are that it didn’t work off the bat. If that’s the case, it is most likely due to incompatible dependencies. The file used by nodules to determine which dependencies your Persevere app needs (and where to find them) is called package.json. You find this file in <path-to-persevere-template>/package.json.

Last time I tried (2011-06-10), I had to change versions for perstore and pintura to “master”, for it to work. Note that changing to “master” is risky – as this is the development trunk version. If you find a combination of numeric version that work together, you’d better stick with them as their code base won’t change.

   "name": "",
   "author": "",
   "dependencies": ["persevere"],
   "contributors": [],
      "perstore": "",
      "commonjs-utils": "",
      "pintura": "",
      "promised-io": "",
      "templify": "",
      "patr": "",
      "rql": "",
      "persevere-client": "jar:!/public/",
      "wiky": "",
      "narwhal": "",
      "jack": "jar:!/lib/jack/",
      "transporter": "",
      "jsgi-node": "jar:!/lib/jsgi-node.js",
      "multi-node": "",
      "tunguska": ""

Relevant links

This entry was posted in JavaScript and tagged , , , , . Bookmark the permalink.
  • Graceland

    That’s really swherd! Good to see the logic set out so well.

  • tom

    It doesn’t work. I got error of “require.path is removed…” when firing up “node ../nodules/lib/nodules.js from folder. I’m using node.js 0.88 stable release.

    So sad :-( . I have the similar error while trying to run persevere-example-wiki.

    Don’t know anyone got it work?!