edx-platform

Files

Victor Shnayder 339e9a68f4 Make end-to-end tests work again

* NOTE: successfully running the tests depends on an updated version of
  django-pipeline, which fixes a unicode bug (efaba4ac63)

Config changes:
* Use separate db for the cms
* Run collectstatic before running tests--needed to get everything in the right place for loading pages
* fix some paths related to this
* Turn off JS compressor for CMS
* add empty test_root/uploads dir

Code changes:
* Add cms tests to check that home page and signup pages load
* Add cms account creation test
* Make github sync tests clean out repo dirs before running.

2012-07-13 11:51:33 -04:00

__init__.py

Moving LMS code into subdirectory

2012-06-06 14:09:01 -04:00

askbotsettings.py

Wip on sign up form.

2012-06-28 15:38:39 -04:00

aws.py

Use relative includes in settings files

2012-06-06 14:16:28 -04:00

common.py

Correctly add course_dirs to static files

2012-07-12 16:06:05 -04:00

content.py

Use relative includes in settings files

2012-06-06 14:16:28 -04:00

dev_edx4edx.py

fix dev_edx4edx mako path - add EDX4EDX_ROOT

2012-07-01 17:44:04 +00:00

dev_ike.py

minor changes - test this branch with more courses (8.01x, 6.00x)

2012-07-08 22:05:21 -04:00

dev.py

Merge remote-tracking branch 'origin/master' into dormsbee/multicourse

2012-07-10 13:39:19 -04:00

devplus.py

Use relative includes in settings files

2012-06-06 14:16:28 -04:00

edx4edx_aws.py

lms/envs/edx4edx_aws update

2012-07-01 12:53:31 -04:00

logsettings.py

Don't swallow messages going to the root logger

2012-07-05 08:48:08 -04:00

README.txt

Moving LMS code into subdirectory

2012-06-06 14:09:01 -04:00

static.py

Use relative includes in settings files

2012-06-06 14:16:28 -04:00

test_ike.py

Use relative includes in settings files

2012-06-06 14:16:28 -04:00

test.py

Make end-to-end tests work again

2012-07-13 11:51:33 -04:00

README.txt

Transitional for moving to new settings scheme. 

To use: 
  django-admin.py runserver --settings=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 envs/dev.py