I’ve taken some time to evaluate the various choices and arrived at the following tooling:

• Ember.js as single-page MVC-framework
• ember-cli as work environment
• Bootstrap as CSSbase

I’ve looked into Emberscript, but it sadly doesn’t yet integrate with ember-cli very well (/at all?).

1. Clone the repo
2. git checkout beekeeper
3. Install ember-cli & dependencies (see below)
4. Install project dependencies
5. Run ember server & visit http://localhost:4200

npm packets:

ember-cli
bower
phantomjs

System wide or local:

• System wide via sudo npm install -g (do I want this?!)
• Locally with npm install

  1. Add a user folder to your PATH, e.g. ~/bin

  2. Syslink every executable manually. Example:

     cd ~/bin ln -s ~/node_modules/ember-cli/bin/ember

Install the projects dependencies (that’s what bower is for): IN <beehive_dir>/beekeeper execute:

bower install

They are thrown inside the vendor/ folder and NOT checked into git.

If you want to learn ember, use the excellent Guide.

The project structure is described at the ember-cli homepage. It changes lots about how you write ember, too, since it integrates an EcmaScript 6 transpiler. Read it.

Ember needs unique object IDs for its persistence backend.

One wants to model the beehive config REST endpoints in a way DS.RESTAdapter can parse it. That includes said object ID, think relational database tables.

1. Create a REST config API in beehive and connect it to embers store & model via DS.RESTAdapter
2. Let the user see available configurated bees & create new ones
3. Let the user see routes and create new ones in style of ifttt.
4. Somehow integrate filters in the process (new filter system?)
5. Export the changes to beehive and let beehive test if they are valid.