Jörn Friedrich Dreyer

was fixed by enabling redis with ``` "STORAGE_USERS_ID_CACHE_STORE": "redis", "STORAGE_USERS_ID_CACHE_STORE_NODES": "127.0.0.1:6379", ```

When creating files and directories via cli they would get assimilated, but the browser listing would not change when reloading the page. The cause was that the web ui somehow...

ok, only issues I am aware of: - [ ] nats-js-kv does not seem to work, fine for now ``` //"STORAGE_USERS_ID_CACHE_STORE": "nats-js-kv", //"STORAGE_USERS_ID_CACHE_STORE_NODES": "127.0.0.1:9233", ``` - [ ] weird web...

This requires being able to list users from remote instances. Our graph DriveRecipients use the ObjectId and a LibreGraphRecipientType ... which is used to differentiate users and groups ... we...

@micbar mentioned [TypeAPI](https://typeapi.org/) introduced in [this blog post](https://chriskapp.medium.com/typeapi-an-alternative-to-openapi-e666eefe8a76) hacker news also [proposes](https://news.ycombinator.com/item?id=35588849) - https://smithy.io/ but most [code generators seem in development](https://github.com/smithy-lang/awesome-smithy?tab=readme-ov-file#client-code-generators) - [fern](https://github.com/fern-api/fern) which also seems to have an [API-first](https://github.com/fern-api/fern?tab=readme-ov-file#api-first)...

What is the current state of this. We found a few bugs that explain why the search service was not scaling. AFAICT we need to reevaluate this with a load...

There are two options. 1. use native GRPC mechanisms to retry. 2. generate go micro clients for the CS3 API. I'd vote the latter, because go micro already retries requests...

Furthermore, I still want to be able to use an in memory transport, which we could use when embracing go micro further.

um ``` # kubectl deploy error: unknown command "deploy" for "kubectl" ``` Did you mean [apply](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#apply)? What `MICRO_REGISTRY` is configured?

@dj4oC @grischdian @blicknix the built in nats in the ocis helm chart cannot be scaled. you have to keep the replica at 1. if you need a redundant deployment use...