SilverSolutions/silverlinux-infra
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document Nextcloud deployment and Infisical secrets

Browse Source
This commit is contained in:
Saeed Asgari
2026-07-08 15:13:17 +03:30
parent a81aa80161
commit 3f94ced9ea
23 changed files with 895 additions and 119 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dbgate/README.md
+6 -6
View File
@@ -55,13 +55,13 @@ Only DbGate is publicly accessible. MSSQL port `1433` and PostgreSQL port `5432`
DbGate requires a username and password before granting access. The initial unauthenticated deployment was corrected by configuring `LOGIN` and `PASSWORD`.
The running server currently stores the DbGate credentials directly in its Compose configuration. The repository intentionally does not contain the password; its Compose definition resolves `DBGATE_PASSWORD` from the deployment environment.
The DbGate password is supplied through Infisical at runtime. The repository intentionally does not contain the password; its Compose definition resolves `DBGATE_PASSWORD` from the deployment environment.
Planned improvement:
Operational requirement:
* Add `DBGATE_PASSWORD` to `/srv/secrets/company.env`.
* Deploy with `docker compose --env-file /srv/secrets/company.env up -d`.
* Remove the credential from the server-side Compose file.
* Keep `DBGATE_PASSWORD` in the DbGate Infisical path.
* Deploy through `slcompose` so the value is injected before Docker Compose evaluates the environment.
* Remove any legacy plaintext credential from the server-side Compose file if it still exists.
---
@@ -120,7 +120,7 @@ Back up:
/srv/docker/dbgate/data
```
Also retain the Compose definition, Nginx Proxy Manager configuration and DbGate credential through the centralized secrets backup after migration.
Also retain the Compose definition, Nginx Proxy Manager configuration and DbGate credential through Infisical recovery.
---