From 6b78680875d9e721d46e4f3d34047c6a3fbd2f33 Mon Sep 17 00:00:00 2001 From: DMRobertson Date: Mon, 1 Nov 2021 11:36:20 +0000 Subject: deploy: ece84f2c450d986e54acc80971225fb02f4e1d05 --- develop/development/cas.html | 8 ++++---- develop/development/database_schema.html | 2 +- develop/development/saml.html | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) (limited to 'develop/development') diff --git a/develop/development/cas.html b/develop/development/cas.html index 77ab326199..1c3f429b80 100644 --- a/develop/development/cas.html +++ b/develop/development/cas.html @@ -190,17 +190,17 @@ easy to run CAS implementation built on top of Django.

  • Create a new virtualenv: python3 -m venv <your virtualenv>
  • Activate your virtualenv: source /path/to/your/virtualenv/bin/activate
  • Install Django and django-mama-cas: -
    python -m pip install "django<3" "django-mama-cas==2.4.0"
    +
    python -m pip install "django<3" "django-mama-cas==2.4.0"
     
  • Create a Django project in the current directory: -
    django-admin startproject cas_test .
    +
    django-admin startproject cas_test .
     
  • Follow the install directions for django-mama-cas
  • Setup the SQLite database: python manage.py migrate
  • Create a user: -
    python manage.py createsuperuser
    +
    python manage.py createsuperuser
     
    1. Use whatever you want as the username and password.
    2. @@ -208,7 +208,7 @@ easy to run CAS implementation built on top of Django.

  • Use the built-in Django test server to serve the CAS endpoints on port 8000: -
    python manage.py runserver
    +
    python manage.py runserver
     
  • diff --git a/develop/development/database_schema.html b/develop/development/database_schema.html index 3f4b14529f..218b677407 100644 --- a/develop/development/database_schema.html +++ b/develop/development/database_schema.html @@ -263,7 +263,7 @@ has had all background updates run.

    To do so, use scripts-dev/make_full_schema.sh. This will produce new full.sql.postgres and full.sql.sqlite files.

    Ensure postgres is installed, then run:

    -
    ./scripts-dev/make_full_schema.sh -p postgres_username -o output_dir/
    +
    ./scripts-dev/make_full_schema.sh -p postgres_username -o output_dir/
     

    NB at the time of writing, this script predates the split into separate state/main databases so will require updates to handle that correctly.

    diff --git a/develop/development/saml.html b/develop/development/saml.html index 8c6b2f212a..040efb558c 100644 --- a/develop/development/saml.html +++ b/develop/development/saml.html @@ -196,7 +196,7 @@ the XML from step 2 as the contents. sp_config: allow_unknown_attributes: true # Works around a bug with AVA Hashes: https://github.com/IdentityPython/pysaml2/issues/388 metadata: - local: ["samling.xml"] + local: ["samling.xml"]
  • Ensure that your homeserver.yaml has a setting for public_baseurl: -- cgit 1.5.1