I set up everything locally in the end. Installing the ‘heroku tool belt’ on my own system and doing their getting started tutorial really helped me. I found copying their file structure from the example (using ejs for views etc) was a bit more intuitive and lightweight than clementine.js. YMMV
I haven’t used clem for any of the microservices yet, but I’m only half way through them. It might become more relevant after the url shortener (which I’m currently on)?
I created (and later deleted) a Github repository from the Clementine project. In the end I found there was too much code for what the project required.Using the timestamp project as an example: my repository contains a file for the server (the back-end which provides the microservice) and a basic HTML page for the front-end interface to the service.
What I aim to do with these projects is to build them on Cloud9 and store the code in Github. That way if someone wants to see what I have done (like a potential employer) then it is easy to do so.
For timestamp and requestHeaderParser this is great. It is not so good for the urlShortener. I miss out on having a full time server running with mongoDB. What I did in that case was to add a “mock database” to the server so the site would run without a connection to mongoDB. So even in this case, someone can download what I have, look at the code, and actually run it.
To sum up, Cloud9 rocks for development (thanks to zaclem01 for the link to get mongoDB working on Cloud9). Clementine is not necessary.
Most importantly: have fun
(if you are not having fun, you are doing it wrong)