Overview
Anysite CLI can load extracted data directly into databases. It supports SQLite (built-in) and PostgreSQL (via optional extra). Connections are stored in ~/.anysite/connections.yaml and can be referenced by name across all CLI commands.
Supported Databases
| Database | Extra Required | Use Case |
|---|
| SQLite | None (built-in) | Local development, single-user workflows, prototyping |
| PostgreSQL | pip install "anysite-cli[postgres]" | Production, multi-user, large datasets |
Add a Connection
anysite db add mydb --type sqlite --database ./data/mydata.db
SQLite databases are created automatically if the file doesn’t exist.First install the PostgreSQL extra:pip install "anysite-cli[postgres]"
Then add the connection:anysite db add pg --type postgres \
--host localhost \
--port 5432 \
--database mydb \
--user app \
--password "$DB_PASSWORD"
Or reference an existing environment variable directly:anysite db add pg --type postgres \
--host localhost \
--database mydb \
--user app \
--password-env PGPASS
Use --password-env to reference an environment variable instead of passing passwords directly. The CLI stores connection details in ~/.anysite/connections.yaml with passwords stored as env var references.
Manage Connections
# List all connections
anysite db list
# Test a connection
anysite db test pg
# Remove a connection
anysite db remove pg
Connection Reference
SQLite Options
| Option | Description | Default |
|---|
--type | sqlite | Required |
--database | Path to the SQLite database file | Required |
PostgreSQL Options
| Option | Description | Default |
|---|
--type | postgres | Required |
--host | Database host | localhost |
--port | Database port | 5432 |
--database | Database name | Required |
--user | Username | Required |
--password | Password (prefer --password-env) | — |
--password-env | Environment variable name containing the password | — |
Next Steps