Paul Fitzpatrick

Results 402 comments of Paul Fitzpatrick

Hmm the operations on this need to be done carefully. It is important not to end up with two workers that both consider themselves responsible for a document. We set...

> I thought a worker could be "reused" if it only experienced a temporary network failure. Because the list of documents affected to workers is available in Redis, it seemed...

Hi @fflorent, yes, if you're up for taking this on when you have bandwidth, then I'd be happy to assign it to you :pray: - just did so.

I don't have a strong opinion about the best strategy. Alex's comment is a good suggestion but shouldn't be taken as holy writ. If some aspect of it requires a...

Grist's origin was as a standalone, downloaded program. Then, work was done to network it in an end-to-end encrypted way, between individual devices, via a dumb hub. This idea excited...

It makes sense. Might need a big "AT YOUR OWN RISK" warning rather than being a default behavior, since otherwise widgets would need to be tested for robustness in reading...

Hi @almereyda, that's interesting! For grist.yml, it would be excellent to get a PR to https://github.com/gristlabs/grist-help that modifies the file such that it passes your validation and also our documentation...

cc @fflorent Thanks for reporting this @illode. For other problems, generally one issue per problem is best.

Thanks @andreapx ! There's a yaml here https://community.getgrist.com/t/a-template-for-self-hosting-grist-with-traefik-and-docker-compose/856. Do you happen to have an example of a web app with a `docker-compose.yaml` that helped you? I see a lot of...

If you don't want https, try `APP_HOME_URL: http://getgrist.local` (remove the `s`). If you do want https, using a proxy is the easiest way to get that (Grist doesn't have built...