You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DATABASE_URL=/usr/db/plume.db
MIGRATION_DIRECTORY=migrations/sqlite
BASE_URL=mission1701.com
# TODO: Put this in a vault
ROCKET_SECRET_KEY=a+qtw6697cIF0cmX7dar33s0SU6JrDemIvWCiLYFv0Ub
When I launch Plume, I get the following error:
$ k logs plume-7c8b66bc8f-jckbh -c install
Configuration read from /app/.env
thread 'main' panicked at 'Couldn't connect to the database.: BadConnection("missing \"=\" after \"/usr/db/plume.db\" in connection info string\n")', plume-cli/src/main.rs:35:40
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Plume version:latest Docker Hub image (0.6.0)
Operating system: Whatever is in the Docker image
Web Browser: Not applicable
The text was updated successfully, but these errors were encountered:
Looks like https://github.com/Plume-org/Plume/blob/main/Dockerfile does not build with the SQLite feature enabled. Not sure why? In my opinion, as the general Docker image for Plume, it should come with support for both database backends.
sssilver
changed the title
BadConnection when configuring for SQLite
BadConnection when configuring for SQLite in Docker
May 21, 2021
Speaking of Docker, the build is currently broken because Rocket requires a very recent Rust Nightly, but the specified toolchain does not satisfy that requirement.
Plume code can't be compiled with support for both PostgreSQL and SQLite at the same time, that is why the docker image only support PostgreSQL. The installation instructions with docker don't mention SQLite for this reason. There could arguably be a second image published with support for SQLite (but not PostgreSQL)
ahangarha
pushed a commit
to ahangarha/Plume
that referenced
this issue
Feb 18, 2022
My configuration looks like this:
When I launch Plume, I get the following error:
latest
Docker Hub image (0.6.0)The text was updated successfully, but these errors were encountered: