Like a turducken or cherpumple, we’re going to stick Ember right into the guts of Django.<\/p>\n
Let’s get this out of the way: this is not ideal. Doing something like having Django power just the API through the Django REST Framework<\/a> and then having Ember do all user-facing things would be smarter. Having the separation is easier for maintenance and clearly defines responsibilities.<\/p>\n Unfortunately, real life is rarely ideal. Your website may have some static pages that necessarily need to be served away from the monolithic stature of Ember, but in keeping assets reusable, they’re still tied into the front end builds. Or you may have deployment requirements that necessitate keeping this tightly bundled. Either way, we’re here now, so let’s figure it out.<\/p>\n Getting Django set up is fairly straightforward, as prescribed by the Django docs<\/a>. The basics on OS X go something like this.<\/p>\n This will install Python 3.x and pyenv, create a virtualenv called I like to structure my Django projects a particular way since they tend to have multiple apps but a singular source of deployment settings.<\/p>\n This does require some changes to fit into this new structure, however.<\/p>\n And remember that you’ll now be doing imports like The cool part about Ember these days is Ember CLI<\/a>, which facilitates a great deal of abiding the framework’s directory requirements. We’ll continue with getting that all set up.<\/p>\n If you’re using Git for source control (and you should be, you dummy), this will create a separate Git repo inside The Django Part<\/h3>\n
\n$ brew install<\/span> pyenv # Additional steps at https:\/\/github.com\/yyuu\/pyenv#homebrew-on-mac-os-x<\/span>
\n$ pyenv virtualenv --python<\/span>=$(<\/span>which<\/span> python3)<\/span> myenv
\n$ pyenv activate myenv
\n$ pip install<\/span> Django<\/span>==1.9.2
\n$ django-admin startproject myapp
\n$ cd<\/span> myapp\/<\/span>
\n$ python manage.py startapp app1<\/div><\/div>\nmyenv<\/span><\/code>, install Django v1.9.2 to it, and then create a skeleton project in the myapp<\/span><\/code> directory with a single app1<\/span><\/code> application.<\/p>\n
\n\u2502 manage.py
\n\u2502 ...
\n\u2502
\n\u251c\u2500\u2500\u2500apps
\n\u2502 \u251c\u2500\u2500\u2500app1
\n\u2502 \u2502 \u2502 models.py
\n\u2502 \u2502 \u2502 views.py
\n\u2502 \u2502 \u2502 ...
\n\u2502 \u2502
\n\u2502 \u251c\u2500\u2500\u2500app2
\n\u2502 \u2502 \u2502 models.py
\n\u2502 \u2502 \u2502 views.py
\n\u2502 \u2502 \u2502 ...
\n\u2502 \u2502
\n\u251c\u2500\u2500\u2500deployment
\n\u2502 \u2502 settings.py
\n\u2502 \u2502 urls.py
\n\u2502 \u2502 ...<\/div><\/div>\n
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
<\/div><\/td>
\n os<\/span>.environ<\/span>.setdefault<\/span>(<\/span>'DJANGO_SETTINGS_MODULE'<\/span>,<\/span> 'deployment.settings'<\/span>)<\/span>
\n
\n# \/deployment\/settings.py<\/span>
\nINSTALLED_APPS =<\/span> [<\/span>
\n 'django.contrib.admin'<\/span>,<\/span>
\n 'django.contrib.auth'<\/span>,<\/span>
\n 'django.contrib.contenttypes'<\/span>,<\/span>
\n 'django.contrib.sessions'<\/span>,<\/span>
\n 'django.contrib.messages'<\/span>,<\/span>
\n 'django.contrib.staticfiles'<\/span>,<\/span>
\n 'apps.app1'<\/span>,<\/span>
\n 'apps.app2'<\/span>,<\/span>
\n]<\/span>
\n
\nROOT_URLCONF =<\/span> 'deployment.urls'<\/span><\/div><\/td><\/tr><\/tbody><\/table><\/div>\nfrom apps.yourapp import models<\/span><\/code> instead of from yourapp import models<\/span><\/code>.<\/p>\nThe Ember Part<\/h3>\n
\n$ npm install<\/span> -g<\/span> ember-cli
\n$ npm install<\/span> -g<\/span> bower
\n$ brew install<\/span> watchman
\n$ npm install<\/span> -g<\/span> phantomjs
\n$ ember new frontendapp<\/div><\/div>\n\/frontendapp\/.git<\/span><\/code>, so you might want to remove that.<\/p>\n