Richie site factory plugin for Tutor
This is a plugin to integrate multiple Richie sites, the learning portal CMS, with Open edX. The integration takes the form of a Tutor plugin.
Dependencies
You should have create your own Richie site factory, go to https://richie.education/docs/cookiecutter/ to know more about it.
Installation
pip install tutor-contrib-richie-site-factory
tutor plugins enable richie-site-factory
Running the Richie plugin will require that you rebuild the "openedx" Docker image:
tutor config save
tutor images build openedx
This step is necessary to install the Richie connector app in edx-platform.
Then, the platform can be launched as usual with:
tutor local quickstart
This plugins allows to run multiple Richie instance sites. So you have to configure each site factory sites so each can be run inside Tutor.
Gettting started
Once your Richie platform is up and running, you will quickly realize that your learning portal is empty. This is because you should first create the corresponding courses and organizations from inside Richie. To do so, start by creating a super user:
tutor local run richie python manage.py createsuperuser
You can then use the credentials you just created at http(s)://yourrichiehost/admin. In development, this is http://courses.local.overhang.io/admin.
Then, refer to the official Richie documentation to learn how to create courses and organizations.
You may also want to fill your learning portal with a demo site -- but be careful not to run this command in production, as it will be difficult to get rid of the demo site afterwards:
# WARNING: do not attempt this in production!
tutor local run richie-<mysite> python manage.py create_demo_site --force
Configuration
This Tutor plugin comes with a few configuration settings:
RICHIE_RELEASE_VERSION(default:"v1.27.1") - the default version of the demo siteRICHIE_HOST(default:"courses.{{ LMS_HOST }}") - the marketing domain name at which the Open edX will be configuredRICHIE_MYSQL_ROOT_USERNAME- (default:{{ MYSQL_ROOT_USERNAME }})RICHIE_MYSQL_ROOT_PASSWORD- (default:{{ MYSQL_ROOT_PASSWORD }})
Other are per site, replace the {site} with the name of your site:
RICHIE_{site}_HOST- (default:{site}.{{ LMS_HOST }})RICHIE_{site}_DOCKER_IMAGE- (default:{{ DOCKER_REGISTRY }}fundocker/richie-demo:{{ RICHIE_RELEASE_VERSION }})RICHIE_{site}_BUCKET_NAME- (default:richie-{site}-uploads)RICHIE_{site}_MEDIA_BUCKET_NAME- (default:richie-{site}-media)RICHIE_{site}_ELASTICSEARCH_INDICES_PREFIX- (default:richie-{site})RICHIE_{site}_CACHE_DEFAULT_BACKEND- (default:base.cache.RedisCacheWithFallback)RICHIE_{site}_CACHE_DEFAULT_LOCATION- (default:redis://{{ REDIS_HOST }}:{{ REDIS_PORT }}/2)RICHIE_{site}_CACHE_DEFAULT_OPTIONS- (default:{})RICHIE_{site}_DJANGO_SETTINGS_MODULE- (default:{site}.settings)RICHIE_{site}_DJANGO_CONFIGURATION- (default:Production)RICHIE_{site}_DB_ENGINE- (default:django.db.backends.mysql)RICHIE_{site}_DB_HOST- (default:{{ MYSQL_HOST }})RICHIE_{site}_DB_NAME- (default:richie_{site})RICHIE_{site}_DB_PORT- (default:{{ MYSQL_PORT }})RICHIE_{site}_DB_USER- (default:richie_{site})RICHIE_{site}_MYSQL_INIT- (default:true)RICHIE_{site}_MYSQL_ROOT_USERNAME- (default:{{ RICHIE_MYSQL_ROOT_USERNAME }})RICHIE_{site}_MYSQL_ROOT_PASSWORD- (default:{{ RICHIE_MYSQL_ROOT_PASSWORD }})RICHIE_{site}_ELASTICSEARCH_HOST- (default:{{ ELASTICSEARCH_HOST }})RICHIE_{site}_EDX_BASE_URL- (default:https://{{ LMS_HOST }})RICHIE_{site}_EDX_JS_BACKEND- (default:openedx-hawthorn)RICHIE_{site}_AUTHENTICATION_BASE_URL- (default:https://{{ LMS_HOST }})RICHIE_{site}_AUTHENTICATION_BACKEND- (default:openedx-hawthorn)RICHIE_{site}_OAUTH2_CLIENT_AUTHORIZED_PATH- (default:None)
If you need to completely customize the production environment, you can use the Tutor patch richie-{{site}}-production-env.
These defaults should be enough for most users. To modify any one of them, run:
tutor config save --set RICHIE_SETTING_NAME=myvalue
For instance, to customize the domain name at which Richie will run:
tutor config save --set "RICHIE_HOST=mysubdomain.{{ LMS_HOST }}"
Development
Bind-mount volume:
tutor dev bindmount richie /app/richie
Then, run a development server:
tutor dev runserver --volume=/app/richie richie
The Richie development server will be available at http://courses.local.overhang.io:8003.
Troubleshooting
Do you need help with this plugin? Get in touch by opening a GitHub issue: https://github.com/fccn/tutor-contrib-richie-site-factory/issues/
Release
- Increase the version in __about.py file, eg. 18.2.0.
- Open a PR and merge it.
- Then create a Git Tag with for the same version, v18.2.0
git tag v18.2.0
git push origin v18.2.0
License
This software is licensed under the terms of the AGPLv3. It was originally developed by Overhang.io with a sponsorship of France Université Numérique. Currently, it's maintained by NAU - FCCN|FCT.
Metadata
Release files for tutor-contrib-richie-site-factory 20.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tutor_contrib_richie_site_factory-20.0.1.tar.gz | 10.7 kB | With provenance | Details for tutor_contrib_richie_site_factory-20.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tutor_contrib_richie_site_factory-20.0.1-py3-none-any.whl | Python 3 | none | any | Details for tutor_contrib_richie_site_factory-20.0.1-py3-none-any.whl |
Total release size: 28.1 kB
Release files / tutor_contrib_richie_site_factory-20.0.1.tar.gz
| Download URL | tutor_contrib_richie_site_factory-20.0.1.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2716aef215961b7309db9e67b11ccfaff6783982cd640c32d18b342e7a67300
|
|
BLAKE2b-256 checksum How to use checksums |
9e27520830f659bf79001a407018725e79487713276db894ae1dd4ed35726444
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 4, 2025.
Transparency logRelease files / tutor_contrib_richie_site_factory-20.0.1-py3-none-any.whl
| Download URL | tutor_contrib_richie_site_factory-20.0.1-py3-none-any.whl |
|---|---|
| Size | 17.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbfa80a14ef7a03292cde154e296f3f49fd560496db2af7972ee57a538930819
|
|
BLAKE2b-256 checksum How to use checksums |
810a728cd6043e42cf03899e04246ebe5f437ad69c38deed987b2afe25d41a3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 4, 2025.
Transparency logSecurity for tutor-contrib-richie-site-factory 20.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for tutor_contrib_richie_site_factory-20.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 4, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.