Podman secrets in .env Datei speichern #31
Labels
No Label
Breaking
Domain
komu.boo
Domain
langrock.info
Domain
libre.moe
Involves
Documentation
Involves
Security
Involves
Testing
Kind
Bug
Kind
Enhancement
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Service
Drone
Service
Element
Service
Gitea
Service
Matrix
Service
Nextcloud
Service
Szuru
Status
Abandoned
Status
Acknowledged
Status
Blocked
Status
Duplicate
Status
Invalid
Status
Need More Info
Status
Won't Fix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: KomuSolutions/igot99issues#31
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Dies dient der Sicherheit beim Bearbeiten von den
compose
Dateien in der öffentlichkeit, um keine secrets zu expose..env
files, besonders wenn man mehrere Nutzen möchte, sind in Podman anscheinend nicht gut umgesetzt und das angeben dieser in einercompose
wird anscheinend nicht respektiert.Using
.env
files has worked in my testing of Revolt, reopening this now