Whenever I update my nakama server, for example with new RPC functions etc. I get
invalid auth token errors as my client is still using the stored token instead.
I’d like to make the server a bit more resilient to this problem, but for that i’d need to know where/how the session gets stored.
As i’m running the server in a Kubernetes cluster with a separate Couchdb instance I would’ve expected this to work, but the fact it doesn’t makes me think sessions get stored on disk instead so i’d need to add some persistence for a specific path to get it working the way I want.
- Versions: Nakama 3.9.0, Docker, Nakama-Unity 3.2.0
- Server Framework Runtime language Go