swcs/cap
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: DB_CONNECTOR

Browse Source
This commit is contained in:
tiago
2025-10-25 13:40:43 +01:00
parent 3a521a3af6
commit b1a6590240
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guide/standalone/options.md
+14 -1
View File
@@ -48,4 +48,17 @@ The `/siteverify` endpoint is intended for server-to-server use, so each request
If you're interested in an option to fully disable ratelimiting, let us know using GitHub issues.
## Custom data path
If you would like the data to be stored in a custom path inside the container, you can set the `DATA_PATH` environment variable to the desired path. Note that this only works in Standalone 2.0.9 or above.
If you would like the data to be stored in a custom path inside the container, you can set the `DATA_PATH` environment variable to the desired path. Note that this only works in Standalone 2.0.9 or above.
## Custom DB connectors
Cap Standalone uses SQLite as the default database for storing keys and challenges. If you'd like to use a different database, you can set the `DB_CONNECTOR` environment variable to the name of the database connector you want to use.
The current accepted values are:
- `bun-sqlite` (default): Bun's built-in SQLite support
- `turso` (experimental): Uses [turso](https://turso.tech/) instead of SQLite.
Both can be exchanged at any time and data won't be lost, however Turso is experimental and doesn't support two or more processes using the same database at the same time (at least at the time of writing).