Database no longer synced by litefs after issue deploying

Hi… The logs and the full Dockerfile (including LiteFS version) are likely to shed light on this, I think, if we could see them. Plus DATABASE_URL (file:///litefs/te.db ?)—with sensitive information removed—which would catch the common problem of writes landing outside FUSE.

It’s non-intuitive, but this on its own is known to cause problems, :dragon:.

(Basically, there are two separate copies of the cluster ID, and they have to be kept in synch.)

Hope this helps a little!