Ponddy Cookie Agreement
The simple cookie agreement implementation and logging user accepting action.
Installation
Normal
Install using pip
pip install ponddy-cookie-agreement
Add cookie_policy to your INSTALL_APPS setting.
INSTALLED_APPS = [
...
'cookie_policy',
]
Add endpoint on your API root urlpatterns
urlpatterns = [
...
path('cookie/policy/', include('cookie_policy.urls')),
]
Use template
Check your TEMPLATES setting already have request context process in your context_processors
TEMPLATES = [
{
...
'OPTIONS': {
'context_processors': [
...,
'django.template.context_processors.request'
],
},
}
]
Add the CSS and JS file and include tag in your template what page you want to show the cookie policy agreement
{% load static %}
<head>
<link href="{% static 'cookie_agreement/cookie.css'%}" rel="stylesheet">
<script src="{% static 'cookie_agreement/cookie.js' %}"></script>
</head>
<body>
{% include 'cookie_agreement.html' %}
</body>
Settings
URLs
COOKIE_POLICY_URL
PRIVACY_POLICY_URL
TERM_OF_SERVICE_URL
THROTTLE
Setting the restful default throttle rates for throttling the accept cookie policy API
DEFAULT_THROTTLE_RATES
Example:
REST_FRAMEWORK = {
'DEFAULT_THROTTLE_RATES': {
'user': '100/day',
'anon': '100/day',
}
}
If you do not want to limit user and your settings already have throttle rates please set user and anon to None
REST_FRAMEWORK = {
'DEFAULT_THROTTLE_RATES': {
'your_other_scope': '100/day',
'user': None,
'anon': None,
}
}
Metadata
Release files for ponddy-cookie-agreement 0.0.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ponddy_cookie_agreement-0.0.9-py3-none-any.whl | Python 3 | none | any | Details for ponddy_cookie_agreement-0.0.9-py3-none-any.whl |
Security for ponddy-cookie-agreement 0.0.9
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.