LiteFS + Caching

[heauton]

I was inspecting litefs.yml and it seemed to me that LiteFS can only proxy a single SQLite file:

proxy:
  ...
  db: '${DATABASE_FILENAME}'

Here are some relevant links I found:
https://community.fly.io/t/litefs-multiple-databases/15595
https://community.fly.io/t/litefs-how-to-work-with-multiple-databases/15472

I am guessing updatePrimaryCacheValue is what acts as a proxy for cache.db (please correct me if I am wrong!)

If for some reason I don't use LiteFS as my main database (use something else e.g., other hosted SQLite, Postgres, etc.), but still use LiteFS only for caching purposes, do I still need to keep this proxy config in litefs.yml? If so, should I update it to look something like this?

proxy:
  ...
  db: '${CACHE_DATABASE_FILENAME}'

Or is it safe to delete this proxy config? I am not sure how this would affect Epic Stack setup, so any help is appreciated. Thanks!

[kentcdodds]

The proxy is only necessary to solve consistency problem: https://github.com/fly-apps/litefs-js

The cache is a bit different since we actually often update the cache on GET requests and we don't want to make the user have to go to the primary on those requests (it defeats the purpose of replicas) which is why we act as our own proxy with updatePrimaryCacheValue. So yes, you're correct, if you're not using litefs for your primary database you can delete the proxy config. Make sure you update your PORT in your Dockerfile to be 8080 since the litefs proxy server won't be listening on 8080 anymore.

[heauton]

Thanks! 😄