mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-27 06:35:54 +03:00
[GH-ISSUE #561] Ability to configure server using environment variables #103
Labels
No labels
bug
compatibility-issue
docker
documentation
enhancement
help wanted
needs information
pull-request
question
stale
unfortunate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-gcs-server#103
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @lisfox1 on GitHub (Aug 26, 2021).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/561
When running this service inside a docker container it would be handy to be able to configure it using env vars instead of cli parameters.
@tustvold commented on GitHub (Sep 2, 2022):
This would be especially useful when using Github Actions which for some inexplicable reason do not support passing command line arguments to services - https://github.com/orgs/community/discussions/26688
@mikechernev commented on GitHub (Jan 11, 2023):
@fsouza mind if I pick up this issue?
@fsouza commented on GitHub (Jan 11, 2023):
Go for it!
@onarres commented on GitHub (Sep 1, 2023):
I created my own docker wrapping the original so I could pass environment variables:
I don't know how to add anything to the main repo to easily add this functionality other than creating a separate docker image that supports this.
@ota2000 commented on GitHub (Mar 8, 2025):
I've continued @vichle ’s work from #1608 and expanded it in #1925 to support all configuration flags with environment variables.
This enhancement improves usability in containerized environments like GitHub Actions service containers.
Key points:
Your feedback and review would be greatly appreciated!
@ota2000 commented on GitHub (Feb 15, 2026):
This has been addressed in v1.54.0 via #1925. The server now natively supports configuration through environment variables. Closing this issue.