Skip to main content
hxlti
============

django app to implement a lti provider


quick start
============

hxlti requires a redis instance running, and by default it will look for
`redis://localhost:6379/0`.

1. add "hxlti" to your INSTALLED_APPS setting like this:

INSTALLED_APPS = [
...
'hxlti',
]

2. include the hxlti urlconf in your project `urls.py` like this:

path('lti/', include('hxlti.urls')),

3. run `python manage.py migrate` to create hxlti models for consumer keys

4. start the development server and visit `http://127.0.0.1:8000/admin/` to
create a consumer (you will need the `Admin` app enabled)

5. configure your lti consumer with the created consumer keys in the previous
step, and use the launch url `http://127.0.0.1:8000/lti/launch/`


other configs
=============

some other settings for hxlti:

# hxlti app settings
HXLTI_ENFORCE_SSL = True # check if request protocol is https, default is false
HXLTI_DUMMY_CONSUMER_KEY = os.environ.get('HXLTI_DUMMY_CONSUMER_KEY', 'dummy')
HXLTI_REDIS_URL = os.environ.get('REDIS_URL', 'redis://localhost:6379/0')

Metadata

Release files for hxlti-djapp 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hxlti-djapp 0.2.1
File Size Uploaded Provenance Actions
hxlti-djapp-0.2.1.tar.gz 4.6 kB Without provenance Details for hxlti-djapp-0.2.1.tar.gz

Release files / hxlti-djapp-0.2.1.tar.gz

Download URL hxlti-djapp-0.2.1.tar.gz
Size 4.6 kB
Tags Source
SHA-256 checksum
How to use checksums
92ca15683c6f07c122fdb5506dd9112c88f77d8306827c3a464740f6cdd1cb1d
BLAKE2b-256 checksum
How to use checksums
06b57b8d7d71724344b786465d67244b774f4d35f212ff1264d10a4ae5f4d545
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.6.4

Security for hxlti-djapp 0.2.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page