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
This wasn't on your target list, but it's a problem I came across recently that would make a good Fly use case.
Algolia is a managed search service. They host your index on a globally distributed network (so it's fast), but if you want to authenticate users, you have to generate a temporary key for them (https://www.algolia.com/doc/guides/security/api-keys/#secured-api-keys).
This means your first call will require a full trip to your backend authentication server, but you can speed that up using edge computing.
Any interest in this becoming an article for Fly?
The text was updated successfully, but these errors were encountered:
Yep! This would be a good one. They even say this in the docs:
Secured API keys are virtual, which means they aren’t stored anywhere, and you can’t find them on the Algolia dashboard. You generate them on the fly
Building little gateways to other services is a good use of Fly.
Sorry, something went wrong.
Moved to Discord: https://community.fly.io/t/secured-api-key-generation-on-the-edge-with-fly/86
No branches or pull requests
This wasn't on your target list, but it's a problem I came across recently that would make a good Fly use case.
Algolia is a managed search service. They host your index on a globally distributed network (so it's fast), but if you want to authenticate users, you have to generate a temporary key for them (https://www.algolia.com/doc/guides/security/api-keys/#secured-api-keys).
This means your first call will require a full trip to your backend authentication server, but you can speed that up using edge computing.
Any interest in this becoming an article for Fly?
The text was updated successfully, but these errors were encountered: