This release is a pre-release and may not be stable for production use.
service-bootstrap
Helper for starting up a service in python
Function start_service()
Usage:
from bootstrap.bootstrap import start_service
config, logger, timezone = start_service()
Configuration
start_service() will look for a config YAML file and load it into a dict,
using the following algorithm:
- if the env variable
CONFIGis defined, it will be used to determine the location of the config file - otherwise a file
./config.yamlis expected to be present
The file will be parsed and returned as a first returned variable
Logging
start_service() will configure the logger will in the following way:
- if
./logging.yamlexists, it will be loaded into a dict and used to configure logging (using dictConfig) - otherwise the default logging format will be applied, which is defined as writing logs on INFO level to stdout
Additionally, start_service() will look for ./loglevels.yaml file with the following structure:
'apscheduler.scheduler': 'ERROR',
'apscheduler.executors.default': 'WARN'
and use this file to configure per-logger log levels. Note that the settings two mentioned above
('apscheduler.scheduler': 'ERROR' and 'apscheduler.executors.default': 'WARN') will be used as a
default.
Finally, start_service() will create a logger called main, log two messages
logger.info("Starting application!")
logger.info("Your timezone is %s" % timezone)
and return this logger as a second returned variable
Timezone
The third returned variable will contain the local timezone as a string (f.ex Europe/Warsaw), detected using
the following algorithm:
- if the env variable
TIMEZONEis defined, it will be used - otherwise timezone will be autodetected using tzlocal
Note on YAML loading
All yaml files are loaded using load_yaml() and may contain env variables!
Function load_yaml()
Usage:
from bootstrap.utils import load_yaml
content = load_yaml("file.yaml")
It will load the content of file.yaml into a dict resolving ENV variables
Metadata
Release files for service-bootstrap 0.0.5.dev1677012300
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 | Reset |
|---|---|---|---|---|
| service_bootstrap-0.0.5.dev1677012300-py3-none-any.whl | Python 3 | none | any | Details |
Release files / service_bootstrap-0.0.5.dev1677012300-py3-none-any.whl
| Download URL | service_bootstrap-0.0.5.dev1677012300-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2593dedf85615f33a4e060643a1d1881ec5247c5b1360737d16e190829310e14
|
|
BLAKE2b-256 checksum How to use checksums |
481e2b96822b5b9a660cb6d2fde4f9eb40fc65becf3ced7436e969a5f006c016
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for service-bootstrap 0.0.5.dev1677012300
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.