1001b315a3
Rather than directly invoke command-line Python (and Mako) from the assets Rakefile, or call an external Python script, use a Django management command to preprocess all asset template files. An "asset template file" is defined as a static asset file with a file extension indicating that it needs to be run through a template engine prior to Sass/CoffeeScript compilation or packaging with other assets. The preprocess_assets management command will look through all of the files listed in the `STATICFILES_DIRS`, preprocessing each as needed. Preprocessing strips off the special template file extension, creating a new file in the process. Currently, the only variable accessible in an asset template file is the `THEME_NAME`, defined in the settings.
Transitional for moving to new settings scheme. To use: rake lms or django-admin.py runserver --settings=lms.envs.dev --pythonpath=. NOTE: Using manage.py will automatically run mitx/settings.py first, regardless of what you send it for an explicit --settings flag. It still works, but might have odd side effects. Using django-admin.py avoids that problem. django-admin.py is installed by default when you install Django. To use with gunicorn_django in debug mode: gunicorn_django lms/envs/dev.py