starred/fake-gcs-server

Fork 0

mirror of https://github.com/fsouza/fake-gcs-server.git synced 2026-04-25 21:55:56 +03:00

[GH-ISSUE #8] How to use? #2155

New issue

Closed

opened 2026-03-15 17:47:19 +03:00 by kerem · 9 comments

kerem commented

2026-03-15 17:47:19 +03:00

Owner

Originally created by @frallain on GitHub (Apr 27, 2018).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/8

Hi, I am really interested by this initiative to mimick GCS a la fakes3. Some questions though,

how to start the server?
what are the dependencies?
Cheers

Originally created by @frallain on GitHub (Apr 27, 2018). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/8 Hi, I am really interested by this initiative to mimick GCS a la fakes3. Some questions though, - how to start the server? - what are the dependencies? Cheers

kerem closed this issue

2026-03-15 17:47:24 +03:00

kerem commented

2026-03-15 17:47:30 +03:00

Author

Owner

@fsouza commented on GitHub (Apr 27, 2018):

@frallain hey, it looks like you want to use this as a standalone server/daemon? fake-gcs-server is a library, you can create a custom application server out of it, but you'd need to write the code to do so.

Not sure if that answers your question. Please let me know if that's not the case! :)

@fsouza commented on GitHub (Apr 27, 2018): @frallain hey, it looks like you want to use this as a standalone server/daemon? fake-gcs-server is a library, you can create a custom application server out of it, but you'd need to write the code to do so. Not sure if that answers your question. Please let me know if that's not the case! :)

kerem commented

2026-03-15 17:47:35 +03:00

Author

Owner

@c1tt1 commented on GitHub (May 2, 2018):

I think it would be better to have make it as standalone daemon or server executable as a rest api service, in that case any programming language can consume it, like how this fake-s3 is implemented . Now as it is only golang developers can use this.

@c1tt1 commented on GitHub (May 2, 2018): I think it would be better to have make it as standalone daemon or server executable as a rest api service, in that case any programming language can consume it, like how this [fake-s3](https://github.com/jubos/fake-s3) is implemented . Now as it is only golang developers can use this.

kerem commented

2026-03-15 17:47:40 +03:00

Author

Owner

@gracenoah commented on GitHub (Aug 6, 2018):

This is how I use it:

package main

import (
	"fmt"

	"github.com/fsouza/fake-gcs-server/fakestorage"
)

func main() {
	server, err := fakestorage.NewServerWithOptions(fakestorage.Options{
		InitialObjects: []fakestorage.Object{
			{
				BucketName: "bucket",
				Name:       "bucket-precreate-object",
				Content:    []byte("This object just forces the bucket to exist when the server starts up."),
			},
		},
		Host:        "0.0.0.0",
		Port:        4443,
		StorageRoot: "/storage",
	})
	if err != nil {
		panic(err)
	}
	fmt.Printf("Server started at %s\n", server.URL())
	select {}
}

I also use it the original intended way as a library with in-memory storage in tests, but this is really useful for integration tests.

@gracenoah commented on GitHub (Aug 6, 2018): This is how I use it: ```go package main import ( "fmt" "github.com/fsouza/fake-gcs-server/fakestorage" ) func main() { server, err := fakestorage.NewServerWithOptions(fakestorage.Options{ InitialObjects: []fakestorage.Object{ { BucketName: "bucket", Name: "bucket-precreate-object", Content: []byte("This object just forces the bucket to exist when the server starts up."), }, }, Host: "0.0.0.0", Port: 4443, StorageRoot: "/storage", }) if err != nil { panic(err) } fmt.Printf("Server started at %s\n", server.URL()) select {} } ``` I also use it the original intended way as a library with in-memory storage in tests, but this is really useful for integration tests.

kerem commented

2026-03-15 17:47:45 +03:00

Author

Owner

@teone commented on GitHub (Mar 27, 2019):

Hi @fsouza,
first thing, thanks for creating this!

I'm trying to use this as a fake backend to create standalone server (as @cllty suggested).
Using @gracenoah suggestion I quickly containerized it and it's running exposing port 9000.

When I run a curl against it I receive a AccessDenied as in:

curl 127.0.0.1:9000/storage/v1/b
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied.</Message><Key>v1/b</Key><BucketName>storage</BucketName><Resource>/storage/v1/b</Resource><RequestId>158FE5F2C8F655B8</RequestId><HostId>7f2ab8aa-98eb-494c-bb79-7d25ec4d7724</HostId></Error>

I couldn't find any reference to credentials in the code, so any guidance on the usage of the server will be much appreciated.

Thanks in advance

@teone commented on GitHub (Mar 27, 2019): Hi @fsouza, first thing, thanks for creating this! I'm trying to use this as a fake backend to create standalone server (as @cllty suggested). Using @gracenoah suggestion I quickly containerized it and it's running exposing port `9000`. When I run a `curl` against it I receive a `AccessDenied` as in: ``` curl 127.0.0.1:9000/storage/v1/b <?xml version="1.0" encoding="UTF-8"?> <Error><Code>AccessDenied</Code><Message>Access Denied.</Message><Key>v1/b</Key><BucketName>storage</BucketName><Resource>/storage/v1/b</Resource><RequestId>158FE5F2C8F655B8</RequestId><HostId>7f2ab8aa-98eb-494c-bb79-7d25ec4d7724</HostId></Error> ``` I couldn't find any reference to credentials in the code, so any guidance on the usage of the server will be much appreciated. Thanks in advance

kerem commented

2026-03-15 17:47:50 +03:00

Author

Owner

@teone commented on GitHub (Mar 27, 2019):

ok, never mind and sorry for the stupid question... I didn't realize the connection was trough https and that's why it was running on port 4443, exposing that port works:

curl --insecure https://127.0.0.1:4443/storage/v1/b
{
  "kind": "storage#buckets",
  "items": [
    {
      "kind": "storage#bucket",
      "ID": "bucket",
      "Name": "bucket"
    }
  ],
  "prefixes": null
}

@teone commented on GitHub (Mar 27, 2019): ok, never mind and sorry for the stupid question... I didn't realize the connection was trough `https` and that's why it was running on port `4443`, exposing that port works: ``` curl --insecure https://127.0.0.1:4443/storage/v1/b { "kind": "storage#buckets", "items": [ { "kind": "storage#bucket", "ID": "bucket", "Name": "bucket" } ], "prefixes": null } ```

kerem commented

2026-03-15 17:47:56 +03:00

Author

Owner

@fsouza commented on GitHub (Mar 28, 2019):

Hey @teone, I think I'll implement a fake--gcs command and containerize that to facilitate testing applications that are not using Go. And would include some docs too. Would that be helpful?

@fsouza commented on GitHub (Mar 28, 2019): Hey @teone, I think I'll implement a fake--gcs command and containerize that to facilitate testing applications that are not using Go. And would include some docs too. Would that be helpful?

kerem commented

2026-03-15 17:48:01 +03:00

Author

Owner

@teone commented on GitHub (Mar 28, 2019):

@fsouza I was waiting to arrive to a more stable point with that but I started looking at that yesterday: https://github.com/teone/gc-fake-storage I'd be happy to contribute this back here if others are interested in it

@teone commented on GitHub (Mar 28, 2019): @fsouza I was waiting to arrive to a more stable point with that but I started looking at that yesterday: https://github.com/teone/gc-fake-storage I'd be happy to contribute this back here if others are interested in it

kerem commented

2026-03-15 17:48:06 +03:00

Author

Owner

@fsouza commented on GitHub (Mar 28, 2019):

Oh cool, if you have it I can link it in the README too :)

@fsouza commented on GitHub (Mar 28, 2019): Oh cool, if you have it I can link it in the README too :)

kerem commented

2026-03-15 17:48:11 +03:00

Author

Owner

@teone commented on GitHub (Mar 28, 2019):