Recommended contents of .env (add some random value for SECRET_KEY and copy the OAUTH2_CLIENT_* values from the .env file on the production server):
DATABASE_URL=postgres://localhost:5432/workbench CACHE_URL=hiredis://localhost:6379/1/?key_prefix=workbench SECRET_KEY=... SENTRY_DSN= ALLOWED_HOSTS=["*"] DEBUG=True NAMESPACE=feinheit OAUTH2_CLIENT_ID=... OAUTH2_CLIENT_SECRET=...
Local setup:
fab setup fab pull_db:fh
Development:
fab dev
Code style & prettification:
tox yarn prettier yarn eslint
Compile the bootstrap library:
yarn build-bootstrap
Metadata
Release files for workbench-crm 0.0.20210124
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 |
|---|---|---|---|---|
| workbench-crm-0.0.20210124.tar.gz | 241.0 kB | Without provenance | Details for workbench-crm-0.0.20210124.tar.gz |
Release files / workbench-crm-0.0.20210124.tar.gz
| Download URL | workbench-crm-0.0.20210124.tar.gz |
|---|---|
| Size | 241.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75da11354d266bb6a9d06a068180f8ec251517e9448e2c60f26285fa713d0dea
|
|
BLAKE2b-256 checksum How to use checksums |
ec11adf3b37a84c34936e89caecf63d225ce48d4f56ea77a87c42404a99c0d40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.52.0 CPython/3.8.5
|
Security for workbench-crm 0.0.20210124
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.