I’ve primarily worked with the Django backend and now want to use ember.js to build the client side presentation. I’ve read @toranb’s replies on the thread Deploying ember with django. I’ve also had a look at ember-django-grunt. However this is more complex that I need for now. Going by the questions asked in the thread, here are my responses
1.) can you leverage something like node.js / npm to build the assets with grunt or do you need something in pure python?
I am not familiar with npm and grunt. I installed them and followed instructions in ember-django-grunt and read up a bit so I think I understand why someone would want to optimise certain tasks, but I’d prefer learning to do without these if possible. I’d rather understand one new thing (ember.js) and get it to integrate with my backend than try mucking about with multiple new things and not understand anything.
2.) what version of django can you use for this project?
Currently on 1.6 and plan to move to 1.7 as soon as it is released.
3.) assuming the answer to #2 is 1.3 / 1.4 / 1.5 -what REST api framework will you layer on top of core django? do you have a preference? I think the major 2 in the wild are /django-rest-framework and tastypie
I’ve picked django-rest-framework
I am planning to start with simple django ORM models.
here is my generic answer w/out knowing any of the above.
First I would scaffold your django models like you would in any django app. Next I would pip install the django-rest-framework (my REST api of choice). Then I would learn grunt to build a client side build step that could compile your handlebars templates (using npm) Finally I would write a really simple ember app that uses a single model from the REST api (running grunt locally to see it all work).
I guess I am not sure about the grunt step… This is most likely coz I am a noob. Do you think I should take a closer look at it if it is going to be that important? In any case I’d like to know how to manage without that if it’s at all possible (and makes sense)