-
Notifications
You must be signed in to change notification settings - Fork 41
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
build tags so that the code could run on Cloudflare and Wazero #123
Comments
@gedw99 This sounds interesting. Could you please give an example of what kind of program you would like to run on both workers and wazero? |
Hey @syumai I am wrote this up a bit better now. Programs that live on your origin server, but where certain things can be offloaded also to CF works, CF R2, etc For example Pocketbase is a very cable server with a SQLITE DB etc. You would run that on your Origin Server. Maybe Hetzner or Fly.io. Then you have all the processing that your need to do, which will use the Pocketbase Sever. Because each wasm file cant be very big the idea is that each Page is its own was file. They both will call the Pocketbase server to access data and do advanced Auth flows that Pocktbase can do. As far as I know the only thing we need to do this is for the Fetch call to be able to run on CF and not on CF. You already. have the asset gen cmd. Maybe a similar thing for the Fetch layer too, so that it's flexible for different runtimes. https://github.com/dispatchrun/net/network/dependents has examples https://github.com/vasilev/HTTP-request-from-inside-WASM is one example. |
Closing due to no response |
I am having a lot of success with workers, but would love to be able to run the workers on Wazero too.
Should we use build tags so that we can run the WASM on Cloud flare but also Wazero ?
The text was updated successfully, but these errors were encountered: