MultiSync
=========
Python script for copying users and groups from a read-only LDAP to several kinds of websites using the Django's ORM.
Currently, synchronization systems are provided for:
* the Django default authentication classes (:class:`django.contrib.auth.models.User` and
:class:`django.contrib.auth.models.Group`),
* the Prosody group system (generates plain config file),
* the PenatesServer groups and users bases (based on the Django's classes).
You only have to provide a configuration file for the application to synchronize and to run `MultiSync` in a crontab (or manually if you prefer).
The expeccted LDAP model is currently tied to the one provided by the `Penates <https://github.com/d9pouces/Penates>`,
but you can easily override it.
The default system is extensible and more synchronizers can easily be added.
More generally, MultiSync relies on a class to synchronize a set of objects against a reference set of objects of same kind,
and you must implement a few virtual methods for each kind a synchronized website.
=========
Python script for copying users and groups from a read-only LDAP to several kinds of websites using the Django's ORM.
Currently, synchronization systems are provided for:
* the Django default authentication classes (:class:`django.contrib.auth.models.User` and
:class:`django.contrib.auth.models.Group`),
* the Prosody group system (generates plain config file),
* the PenatesServer groups and users bases (based on the Django's classes).
You only have to provide a configuration file for the application to synchronize and to run `MultiSync` in a crontab (or manually if you prefer).
The expeccted LDAP model is currently tied to the one provided by the `Penates <https://github.com/d9pouces/Penates>`,
but you can easily override it.
The default system is extensible and more synchronizers can easily be added.
More generally, MultiSync relies on a class to synchronize a set of objects against a reference set of objects of same kind,
and you must implement a few virtual methods for each kind a synchronized website.
1 maintainer
Metadata
1 maintainer
Release files for multisync 0.5.3
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 | |
|---|---|---|---|---|
| multisync-0.5.3.tar.gz | 26.3 kB | Without provenance | Details |
Release files / multisync-0.5.3.tar.gz
| Download URL | multisync-0.5.3.tar.gz |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64ddc60e6157701cc04d203054c4ccbeafb7155996a113ce3ce3c6975a261543
|
|
BLAKE2b-256 checksum How to use checksums |
2f4c6fba85621b36ddcd1c1cad22b69682552d7709b2186749cca04e86f9d1a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for multisync 0.5.3
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.
