You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mimir single binary should "just work" with the default config. Ideally, a single test replica of Mimir should run locally with no custom config but that's probably too much: stretching this a bit, we should require as least as config as possible to start it up.
Change default blocks_storage.backend to filesystem
This seems like a very strange default value, with limited use.
But perhaps better than failing with s3 being the default.
This was my thinking behind it that for all other blocks_storage.backends, you are required to set at least a bucket name or some form of authentication, while we could filesystem without further consideration.
I guess it can go horribly wrong if the filesystem is used with multiple instances and the folder is not shared by them.
Mimir single binary should "just work" with the default config. Ideally, a single test replica of Mimir should run locally with no custom config but that's probably too much: stretching this a bit, we should require as least as config as possible to start it up.
blocks_storage.backend
tofilesystem
#831The text was updated successfully, but these errors were encountered: