datapress 0.4.3

Single `datapress` binary bundling both the DuckDB and DataFusion dataset HTTP backends, selectable at runtime via `server.backend`.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63

# datapress

A single `datapress` binary that bundles **both** dataset HTTP backends —
DuckDB and DataFusion — and picks the active one at runtime from
`server.backend` in your `datasets.toml`.

```sh
cargo install datapress    # installs the `datapress` binary
datapress                  # serves using the resolved datasets.toml
```

## Configuration file

`datapress` resolves its config in this order (first match wins):

1. `--config <FILE>` flag
2. `$DATAPRESS_CONFIG_FILE` environment variable
3. `./datasets.toml` (current directory)
4. `$HOME/datasets.toml`

Generate a starter config with the `init` subcommand. It writes a
commented `datasets.toml.template` to the given directory, or your home
directory when omitted:

```sh
datapress init                 # writes ~/datasets.toml.template
datapress init ./config        # writes ./config/datasets.toml.template
datapress init --force         # overwrite an existing template

# then:
cp ~/datasets.toml.template ~/datasets.toml   # and edit
datapress
```

## Choosing a backend

```toml
# datasets.toml
[server]
backend = "duckdb"      # or "datafusion"
```

## Slimmer single-backend builds

Both backends are compiled in by default. To build just one:

```sh
cargo install datapress --no-default-features --features duckdb
# or
cargo install datapress --no-default-features --features datafusion
```

## Optional features

`docs`, `swagger`, `metrics`, and `auth` are forwarded to whichever
backends are enabled, e.g.:

```sh
cargo install datapress --features swagger,auth,metrics
```

See the [workspace README](https://github.com/jeroenflvr/datapress) for full
configuration details.