JMS use the idea called "Negative loading" presented at JSConf EU 2012.
For more information on JMS, I recommend my talk at Craft conf 2014.
It's still under development.
git clone https://github.com/ustream/jms.git cd jms sudo npm install pm2 -g npm install
Every command can handle the
--config <configname> parameter,
to load separate config files.
JMS stores data in redis, for a quick install on osx, run
brew install redis redis-server /usr/local/etc/redis.conf > /dev/null &
The deploy script handle two optimal parameters:
./jms deploy [repository] [--config <configname>]
repository is the key from
configname is the configuration from
For a quick, example code, run
./jms deploy dev --config local
If you haven't modified the configs, it will deploy all the small codebase from examples/dev.
Start a JMS server using the local config
examples/dev.html in your browser to see it work, open the dev console, for more info.
After this, try to deploy the live code, and open
examples/index.html, and play around.
To clear the internal cache
./jms purge [--config <configname>]
To remove a single source repo cache
./jms purge repoId [--config <configname>]
To stop the server
restart | reload
To restart the server
To get some status info
It should output something like this
JMS online with 8 processes concurrent requests 0 requests / sec 0 cpu usage (%) 0 memory usage (MB) 312 total requests served 6 exits per sec 0