CMS Attendance
Manage and monitor attendance of users sharing a common WiFi, using a specialized WiFi hotspot module.
This plugin is only intended to be used with a CMS project, and not directly in any django project. To use in an independent django project, you might need to configure your project.
Features
Track & monitor presence of a user, automatically after initial setup
Extract comprehensive reports & logs via GraphQL APIs
Requirements
An ESP8266 or other compatible WiFi module needs to running for the attendance to be recorded.
The ESP8266 must be flashed with Module script .
User’s machines must also must be installed with Client script.
1 maintainer
Metadata
1 maintainer
Release files for cms-attendance 0.1.3.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 |
|---|---|---|---|---|
| cms-attendance-0.1.3.1.tar.gz | 19.2 kB | Without provenance | Details for cms-attendance-0.1.3.1.tar.gz |
Release files / cms-attendance-0.1.3.1.tar.gz
| Download URL | cms-attendance-0.1.3.1.tar.gz |
|---|---|
| Size | 19.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96bd66a38553ab5807544827818ff49d4e68564013b09ba7f74eff0b34b15060
|
|
BLAKE2b-256 checksum How to use checksums |
4ff064bffaaaa4c6293396fc5d6b81aa1707218d6b549bb245c0d9b9169b7b1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.3
|
Security for cms-attendance 0.1.3.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.
