74b9a2a408
local.yaml is only loaded in the local environment, and will not be used in production. To avoid specifying it in both production and local configurations, use it as a default specified in the code instead (that's the pattern we're using in other places too from what I remember, maybe we should refactor that too, but that's a bigger task not tied to this change). **Tested by** On a local dev cluster - Not specifying anything and ensuring that the default is picked - Specifying an override in museum.yaml and verifying that is used instead |
||
---|---|---|
.. | ||
authenticator | ||
cast | ||
datacleanup | ||
embedding | ||
kex | ||
passkey | ||
remotestore | ||
storagebonus | ||
two_factor_recovery | ||
userentity | ||
billing.go | ||
collection.go | ||
family.go | ||
file.go | ||
file_size.go | ||
notificationhistory.go | ||
object.go | ||
object_cleanup.go | ||
object_copies.go | ||
public_collection.go | ||
push.go | ||
queue.go | ||
srp.go | ||
tasklock.go | ||
trash.go | ||
twofactor.go | ||
usage.go | ||
user.go | ||
userauth.go |