SOATO Registry
SOATO Registry of Uzbekistan
Documentation
The full documentation is at https://uzsoato_registry.readthedocs.io.
Quickstart
Install SOATO Registry:
pip install uzsoato_registry
Add it to your INSTALLED_APPS:
INSTALLED_APPS = (
...
'rest_framework',
'django_celery_beat',
'soato',
...
)
Add settings for celery:
CELERY_BROKER_URL = "redis://127.0.0.1:6379/0"
Add settings for static files:
STATIC_URL = "/static/"
STATUC_ROOT = os.path.join(BASE_DIR, "statis")
MEDIA_URL = "/media/"
MEDIA_ROOT = os.path.join(BASE_DIR, "media")
Add Tashkent address registry’s URL patterns:
urlpatterns = [
...
path('soato/', include('soato.urls', namespace="soato"),
...
]
Features
TODO
Running Tests
Does the code actually work?
source <YOURVIRTUALENV>/bin/activate (myenv) $ pip install tox (myenv) $ tox
Development commands
pip install -r requirements_dev.txt invoke -l
Credits
Tools used in rendering this package:
History
0.1.0 (2021-04-10)
First release on PyPI.
Metadata
Release files for uzsoato-registry 0.1.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 | Actions |
|---|---|---|---|---|
| uzsoato_registry-0.1.3.tar.gz | 134.4 kB | Without provenance | Details for uzsoato_registry-0.1.3.tar.gz |
Release files / uzsoato_registry-0.1.3.tar.gz
| Download URL | uzsoato_registry-0.1.3.tar.gz |
|---|---|
| Size | 134.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fcbab1b8d5a1e34b24f24fb2ba3f6d1e37426bfd31ab0614cc9ec3de7d8230c
|
|
BLAKE2b-256 checksum How to use checksums |
bf1711ab07bd8965c960e032a68900b275395036b9b31c679691183e227392d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.7
|
Security for uzsoato-registry 0.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.