-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
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
Question about cloud edge functions support #161
Comments
Creating a |
I will test it before I start my project. If I encounter any problems, I will report them or make a PR. |
Tested with Cloudflare Workers (local dev mode) but the
It seems some packages or features are not supported by Cloudflare Worker. Is it possible to avoid using shim in Fedify for better capabilities? |
We're willing to support edge functions including Cloudflare Workers in a long term, but I guess it wouldn't be trivial in a short term… 😭 One cloud edge function I've tested with Fedify is Deno Deploy at the moment. |
Ah, Fedify on JSR would work better with edge functions. |
Switching to
|
Updated: Fixed, the typo caused the web finger not to return anything. I can run it correctly after adding polyfill. According to the tutorial - https://fedify.dev/tutorial/basics#actor-dispatcher I can call |
Could you try a polyfill for Temporal API? |
Hi,
I find the microblog document has some notes about
Recently, cloud edge functions like Cloudflare Workers have also gained popularity as JavaScript runtimes
Does Fedify expect to support it natively?
If I choose to use Cloudflare Workers, I need to use the Bindings feature to get the key-value store.
However, the
Federation
object is requiredkv
and initialized before handling the request.Or the expected usage is like this
The text was updated successfully, but these errors were encountered: