We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wanted to start a thread to gather/contribute ideas for distributed pico.
Distributed pico involves deploying instances of pico on multiple servers around the world primarily for reducing ping.
The text was updated successfully, but these errors were encountered:
While reading about Caddy's TLS settings, I learned you might need to store the TLS certs in some shared storage system. Minio/S3 seems like it may be the easiest.
You can import all the current certs into Minio like this: https://caddyserver.com/docs/command-line#caddy-storage
Sorry, something went wrong.
If you end up deploying minio in multiple regions, I stumbled across this S3-compatbile storage project that is specifically designed to handle high latencies between instances: https://garagehq.deuxfleurs.fr/documentation/reference-manual/features/
They handle consensus differently (using CRDTs) which avoids the need for a "leader" and reduces the number of slow intra-cluster requests: https://garagehq.deuxfleurs.fr/documentation/design/benchmarks/
One internal detail is that small objects are stored in the replicated metadata itself, and that threshold is 3072 bytes, which is great for storing _headers and _redirects.
_headers
_redirects
No branches or pull requests
Wanted to start a thread to gather/contribute ideas for distributed pico.
Distributed pico involves deploying instances of pico on multiple servers around the world primarily for reducing ping.
The text was updated successfully, but these errors were encountered: