1
0
Fork 0
kubernetes/firefly-iii
Dustin a269f8a1ae firefly-iii: Connect to external PostgreSQL
Since the new database server outside the Kubernetes cluster, created
for Authelia, was seeded from a backup of the in-cluster server, it
already contained the data from Firefly-III as well.  Thus, we can
switch Firefly-III to using it, too.

The documentation for Firefly-III does not mention anything about how
to configure it to use certificate-based authentication for PostgreSQL,
as is required by the new server.  Fortunately, it ultimately uses
_libpq_, so the standard `PG...` environment variables work fine.  We
just need a certificate issued by the _postgresql-ca_ ClusterIssuer and
the _DCH Root CA_ certificate mounted in the Firefly-III container.
2024-07-02 18:16:05 -05:00
..
.gitignore firefly-iii: Deploy Firefly III 2023-05-14 11:15:15 -05:00
firefly-iii-importer.env firefly: importer: Set VANITY_URL 2023-12-10 08:39:13 -06:00
firefly-iii.env firefly-iii: Connect to external PostgreSQL 2024-07-02 18:16:05 -05:00
firefly-iii.yaml firefly-iii: Connect to external PostgreSQL 2024-07-02 18:16:05 -05:00
importer-ingress.yaml firefly-iii: Use a single Data Importer instance 2023-12-10 08:55:20 -06:00
importer.yaml firefly-iii: Use a single Data Importer instance 2023-12-10 08:55:20 -06:00
ingress.yaml firefly: ingress: Increase max body size 2023-12-01 22:04:07 +00:00
kustomization.yaml firefly-iii: Connect to external PostgreSQL 2024-07-02 18:16:05 -05:00
postgres-cert.yaml firefly-iii: Connect to external PostgreSQL 2024-07-02 18:16:05 -05:00
redis.yaml firefly-iii: Use volume claim template for redis 2024-06-26 18:29:49 -05:00
secrets.yaml firefly-iii: Replace importer access token 2024-05-10 09:23:04 -05:00