Option to override the database check

[matthias-hoste]

I recently attempted to install TaxHacker on docker. I have an existing postgresql database so I opted to use that one instead of hosting another.
When using username taxhacker-user and database name taxhacker the database check will never succeed because it cuts off the database at the end causing taxhacker-user to be used as database name which doesn't exist and thus taxhacker never fully starts.

It would be nice if it's possible to define an environment variable that overrides this check and will just start to apply migrations regardless

[vas3k]

Can you describe in more detail how you run the docker image?

Do you specify env variable DATABASE_URL="postgresql://your-user@localhost:5432/your-database-name"? It should use that for provisioning

You can also try to build the image yourself with a host-hosted postgres using a docker-compose file like this:

services:
  app:
    build:
      context: .
      dockerfile: Dockerfile
    ports:
      - "7331:7331"
    environment:
      - SELF_HOSTED_MODE=true
      - UPLOAD_PATH=/app/data/uploads
      - DATABASE_URL="postgresql://your-user@host.docker.internal:5432/your-database-name
    volumes:
      - ./data:/app/data
    restart: unless-stopped
    extra_hosts:
      - "host.docker.internal:host-gateway"