Closed Sapp00 closed 1 day ago
Okay, actually just some documentation is outdated. It should be DB_CONNECTION
and not DB_TYPE
to define the database type. Furthermore, this PR is needed to get it running.
Afterwards, there are still errors:
SQLSTATE[42804]: Datatype mismatch: 7 ERROR: column "enabled_expense_tax_r ates" cannot be cast automatically to type integer HINT: You might need to specify "USING enabled_expense_tax_rates::integer" . (SQL: ALTER TABLE companies ALTER enabled_expense_tax_rates TYPE INT)
There is a fork where this issue has been "fixed": patch file. It is out of date and also rather hacky than clean.
Setup information Docker, deployed on Kubernetes using Custom Deployment
Describe the bug The container starts, but after a long time it crashes saying that the MySQL Server is gone while I set the environment variable to use Postgres. When I jump into the container, the Environment Variable shows:
Somehow this variable is being ignored.
To reproduce Steps to reproduce the behavior:
Expected behavior It should connect to the postgres.
Screenshots/logs
Docker/Kubernetes/Helm:
Additional context I execute it without root privileges - do I need to specify gid/uid? It at least doesnt show any privilege issues.
Deployment: