node package manager


Lively Kernel

Lively Kernel is a web-based runtime and development environment that makes creation of web applications much more immediate and direct. Please see for more general information about the Lively Kernel project.

For feedback, announcement and discussions, please feel invited to subscribe to our mailing list.

This repository is a fork of the Lively Kernel Webwerkstatt wiki at HPI. To learn more about the motivation and long-term vision for this repository see the wiki.


Get Lively Kernel core up and running.


  1. node.js: In a terminal try running node -v. If that fails install node.js.

  2. npm: Try running npm -v. If that fails run curl | sh in your terminal to install it.

Running Lively

  1. Clone the Lively Kernel repository.
git clone ~/LivelyKernel
  1. Go into the Lively Kernel directory and run npm:
cd ~/LivelyKernel
npm install
  1. In that directory start the minimal server
lk server

That's it. You can now visit a rather boring page blank.xhtml workd or run the tests with lk test.

Setup an apache server

Note 1 You only need to do this if you want to run a full-fletched Lively Kernel installation that provides the functionality to run a Lively Wiki.

Note 2 We are currently working on a pure node.js solution to get rid of apache and the complicated setup process.

See installation notes for apache on Debian and Mac OS x for details.

Installing the Webwerkstatt PartsBin

You can install all the cool tools from Webwerkstatt's PartsBin. Have a look at the HOWTO.

Running the tests

Command line tests

Note: Make sure you have all required node.js modules installed. Run npm install to do so. To start the Lively tests from the command line first start the server:

lk server

To initiate a test run do

lk test

This runs tests in the browser you specified in testing/config.js. See lk test --help for all the test runner options.

LivelyKernel on Travis-CI

We use Travis-CI to run tests continuously on every commit into the Master branch: Build Status


Please this wiki page for some best practices to work with git and github.