Developers can have private settings files by creating
lms/envs/private.py or cms/envs/private.py.  They are imported
at the end of dev.py.  Note that they won't be imported if you
are using one of the other dev*.py variants.

Feature/cdodge/allow setting of session cookie name

Ensure that the original error gets preserved by the ErrorModule

allow configuration settings to specify a session cookie name. This is to avoid problems we are experiencing between simultaneous login sessions between edx.org and edge.edx.org on certain browsers (i.e. Firefox)

allow configuration settings to specify a session cookie name. This is to avoid problems we are experiencing between simultaneous login sessions between edx.org and edge.edx.org on certain browsers (i.e. Firefox)

Jonahstanley/fix codemirror tests

Expose site-wide anonymized ids to HTML module

Use coffee watch command to watch whole directories, so that it will pic...

It turns out that code mirror things can be edited.  Once the div is clicked, a new text area appears that can be obtained and sent keys

Unbreak acceptance tests in the cms.

Specify UTF-8 encoding when loading Mako template

LMS Slim Header Visual Clean-Up

Turn off automatic snapshot to tmp dir on lettuce failure

lms - revises the physical height of the edX logo within the slim-sized header and vertically aligns all elements

Add comment to dynamically-generated asset files

To avoid confusion about where these files come from, add a header
comment upon preprocessing that warns people to not modify the
generated files directly, and points them to the appropriate
template file.

Peter fogg/single click video creation

adding sympy and networkx

Fix bug STUD-103. The url base for about page links needs to be www.edx....

Use coffee watch command to watch whole directories, so that it will pick up new coffee files as they are created

Studio - Advanced Component Icon

Fix/btalbot/edx.org accessibility

edx.org - revises login and register graphical banner images to include higher contrast between type and imagery

When loading a Mako template from a Django template, the file
encoding of the Mako template was left unspecified. In some cases,
this would cause the Mako template to be interpreted as an ASCII
template, resulting in blowups if the template was encoded in
UTF-8 (e.g., lms/templates/footer.html).

Now, both the input and output encodings are specified as UTF-8.