| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| djangoapps | ||
| envs | ||
| lib | ||
| static | ||
| templates | ||
| README.rst | ||
| __init__.py | ||
| celery.py | ||
| startup.py | ||
| tests.py | ||
| urls.py | ||
| wsgi.py | ||
| wsgi_apache_lms.py |
Per Dave Ormsbee: > That was from way back when, when we actually had Django server pools, > proxied differently by nginx; one was the courseware, and the other > was askbot, a discussion forum. > > They shared all the same code, but different parts were live. It was > about as good an idea as it sounds. > > There is no reason that I can think of in the current day and age where > you would ever want to run the LMS and *turn off courseware*.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| djangoapps | Loading commit data... | |
| envs | Loading commit data... | |
| lib | Loading commit data... | |
| static | Loading commit data... | |
| templates | Loading commit data... | |
| README.rst | Loading commit data... | |
| __init__.py | Loading commit data... | |
| celery.py | Loading commit data... | |
| startup.py | Loading commit data... | |
| tests.py | Loading commit data... | |
| urls.py | Loading commit data... | |
| wsgi.py | Loading commit data... | |
| wsgi_apache_lms.py | Loading commit data... |