I’ve taken some time to evaluate the various choices and arrived at the following tooling:
I’ve looked into Emberscript, but it sadly doesn’t yet integrate with ember-cli very well (/at all?).
- Clone the repo
git checkout beekeeper
- Install ember-cli & dependencies (see below)
- Install project dependencies
- 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
-
Add a user folder to your PATH, e.g.
~/bin
-
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.
- Create a REST config API in beehive and connect it to embers store & model via DS.RESTAdapter
- Let the user see available configurated bees & create new ones
- Let the user see routes and create new ones in style of ifttt.
- Somehow integrate filters in the process (new filter system?)
- Export the changes to beehive and let beehive test if they are valid.