This release is a pre-release and may not be stable for production use.

## Installation
```bash
python -m pip install vizbee
```
optionally the target(s) data source an be passed as argument to install
required dependencies:
```bash
python -m pip install vizbee[<source>]
```
where `<source>` is one of:
* postgresql
* oracle
* mysql
* redshift
* sqlserver
* sybase
## Usage
```bash
Usage: vizbee [OPTIONS] COMMAND [ARGS]...
Options:
-c, --config TEXT The YAML configuration file path.
--client-id TEXT The application id.
--client-secret TEXT The application secret.
--api-url TEXT The api url.
--help Show this message and exit.
Commands:
dashboard Manage dashboards.
dataset Manage datasets.
start Start scheduler.
sync Push all datasets and dashboards.
```
## Connections
This section defines the connections to the data stores
(the ``default`` field sets the default one).
```yaml
connections:
default: {DATABASE_URL}
```
Currently supported database are:
* PostgreSQL: `postgresql://<user>:<password>@<host>/<db>`
* MySQL: `mysql://<user>:<password>@<host>/<db>`
* Oracle: `oracle://<user>:<password>@<host>/<db>`
* Redshift: `redshift://<user>:<password>@<host>/<db>`
* SQLServer: `mssql://<user>:<password>@<host>/<db>`
## Datasets
A `Dataset` represents a single set of data:
```yaml
datasets:
my-dataset:
name: <The dataset name>
connection: <The connection to use>
query: <The query used to fetched data>
graph: <The graph options>
schedule: <The scheduling rule>
```
See [dataset schema](https://vizbee.io/documentation/schema#dataset) for more details.
## Dashboards
A `Dashboard` represents a `Dataset` collection:
```yaml
dashboards:
my-dashboard:
name: <The dashboard name>
datasets:
- <The datasets to include>
```
See [dashboard schema](https://visbee.io/documentation/schema#dashboard) for more details.
## Scheduling
The agent can be started as a daemon to schedule datasets update,
it require to define a scheduling rule such as:
```yaml
schedule: 5 minutes
```
and the start the deamon:
```bash
vizbee start
```
For each `Dataset` the scheduling rule can be overriden by adding a
`schedule: <rule>` in its schema.
The scheduling rule format is: `<count> <seconds|minutes|hours|days>`
Metadata
Release files for vizbee 0.1b1
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 |
|---|---|---|---|---|
| vizbee-0.1b1.tar.gz | 6.2 kB | Without provenance | Details for vizbee-0.1b1.tar.gz |
Release files / vizbee-0.1b1.tar.gz
| Download URL | vizbee-0.1b1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d24fd75a39df808069c27131b2500739b8b7538b4e7bc67a2210d707472b4d7d
|
|
BLAKE2b-256 checksum How to use checksums |
60ee9959b4bd86b8be3531bd92fc72e263cb726d6e7bb9a5ba10da83ff8d8af4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for vizbee 0.1b1
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.