I’ve been trying to do this for a while and not having success. The idea is to have a litefs volume attached to a primary, and so I thought there is no need for replicas to have a volume since they are simply synced from the primary. Any help or advise on this would be greatly appreciated. Thank you.
It’s good to have sane defaults that a volume is always created, but it’s not clear how to disable it.
fly machine clone - there is --attach-volume option, but no “disable volume” option.
fly scale count x - no options relating with volumes when I tried --help
Also on a side question, is it possible to have litefs “candidates” across different regions, each can write and forward to the primary seamlessly?
Hi… You might be thinking of / remembering the LiteVFS (with the “V”) sub-project:
There was only a single post about it, that I recall, and presumably the sunsetting of LiteFS Cloud means that a non-trivial restructuring would have been needed, even if it was still active…
Regarding the broader question about volumes…
It should be possible via “process groups”—namely having the primary-candidates in one group and everything else in the other. The [mounts] section of fly.toml should allow the restriction of the volumes to the first.
That may not be wise with the usual LiteFS (without the “V” now), although I have to admit that I’m slightly tempted to try it out myself now, with a throwaway cluster…