Django2 app for creating Alexa Skills
Django app for easily creating Amazon Alexa Skills. By Tim Woocker & Malte Mosler
Table of Content
1. Prerequisites
If you're using Apache HTTP Server, use v2.4.10 or later! From Amazon's Docs:
Note: if you are using Apache HTTP Server to host your web service, use version 2.4.10 or later. Earlier versions of Apache HTTP Server send an "unrecognized name" warning if the server is not configured with a ServerName or ServerAlias in the configuration files. This prevents the Alexa service from sending the customer's request to your server. To address this, either upgrade to 2.4.10 or later, or add ServerName / ServerAlias to your server's configuration file.
2. Getting Started
You can use pip to install this app:
pip install django2-alexa
In your django settings.py add "django2_alexa" to INSTALLED_APPS:
INSTALLED_APPS = [
...
'django2_alexa',
...
]
In your current path create a django app with:
python manage.py startapp YourAppName
Import & create the Skill object in your views.py:
from django2_alexa.interfaces.alexa import Skill
skill = Skill()
Import the skill in your urls.py and add the view to your urlpatterns:
from YourAppName.views import skill
urlpatterns = [
...
path('', skill.view)
...
]
You can use this library with DEBUG mode on in settings.py. The amazon server verification for timestamps however will be skipped. This will cause amazon to not accept your skill if you try to publish your skill in DEBUG mode.
Now you are ready to develope your own skill for alexa! You can find a few examples here.
3. Settings
This django app adds some settings to your project:
| Name | Type | Default | Description |
|---|---|---|---|
ALEXA_VERIFY_CONN |
bool |
True |
This setting specifies if every request to an alexa skill should be verified against the amazon servers. This is useful when testing your skill without Amazon's service. |
4. Examples
5. Support
Twitter: @Tim Woocker @DeemonRider
Metadata
Release files for django2-alexa 0.1.4
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 |
|---|---|---|---|---|
| django2-alexa-0.1.4.tar.gz | 8.0 kB | Without provenance | Details for django2-alexa-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django2_alexa-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for django2_alexa-0.1.4-py3-none-any.whl |
Total release size: 27.0 kB
Release files / django2-alexa-0.1.4.tar.gz
| Download URL | django2-alexa-0.1.4.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6003095dd041e8a7f947a479301695f6cb8bc642b57903b8a75348f7b8e44cb
|
|
BLAKE2b-256 checksum How to use checksums |
b3e3feceee5aee01d8754a6b0715bd84c5c79f682981f66ad05b693dc80015eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.5.2
|
Release files / django2_alexa-0.1.4-py3-none-any.whl
| Download URL | django2_alexa-0.1.4-py3-none-any.whl |
|---|---|
| Size | 19.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a5defa606c41fd899e21c3811e591efe523a1dc7a21964b0bd1635d0154c11d
|
|
BLAKE2b-256 checksum How to use checksums |
2a94353b8f9631151b3519e5b15a5b647e4f9249438d80c4f11391f7a6273dc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.5.2
|
Security for django2-alexa 0.1.4
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.