mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-25 13:45:52 +03:00
[GH-ISSUE #587] Update examples to include documentation on how to run/required configuration #106
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#106
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 @potatochip on GitHub (Sep 30, 2021).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/587
Raises error from gcs client
@fsouza commented on GitHub (Oct 1, 2021):
Can you provide more details? Which command did you run? How did you start the server? What error did you get?
@potatochip commented on GitHub (Oct 1, 2021):
@fsouza commented on GitHub (Oct 1, 2021):
Oh I see, it's trying to connect to the real server, you need to set the endpoint, either via an environment variable or the proper parameters in the client.
Take a look on how we do it in CI: https://github.com/fsouza/fake-gcs-server/blob/main/ci/run-python-example.sh.
@potatochip commented on GitHub (Oct 5, 2021):
Thanks for checking. It does work after doing that. Might want to update documentation to mention env var or other options in order to get things working.
@fsouza commented on GitHub (Oct 5, 2021):
Do you think that replicating the comment at the top of the Go example is enough or do we need more?
@potatochip commented on GitHub (Oct 5, 2021):
Should be fine
On Tue, Oct 5, 2021 at 10:57 AM francisco souza @.***>
wrote:
@wwwjn commented on GitHub (Apr 22, 2022):
Same problem make me stuck for a while! I believe we might need better documentation for examples. (Cause It's very easy to ignore the comment on the top.
@fsouza commented on GitHub (Apr 22, 2022):
@wwwjn where do you think we should put the documentation?
@wwwjn commented on GitHub (Apr 22, 2022):
Thanks a lot for your quick response! For example, we can add a short markdown file in the /examples folder.
Btw, Thanks for create such a great project!
@fsouza commented on GitHub (Apr 22, 2022):
That's a good idea! We can add the markdown file with the generic information that applies to all examples and then have some inline comments in the code whenever there are any specifics. I will try to find time to work on that on the weekend or early next week.
@somen440 commented on GitHub (May 1, 2022):
I had a similar problem. The sample worked locally with the following command.