You need to put it like “git+https://git.server.com/user/project.git”, but as above workers doesn’t
You need to put it like “git+https://git.server.com/user/project.git”, but as above workers doesn’t built the project your computer or CI script does
Jthat's weird, maybe I messed something up with the authorization then, thanks :)
Update: Fixed, the package was broken, thx for your answers!
Update: Fixed, the package was broken, thx for your answers!
QYo this Wrangler documentation ain't lit.
I've seen both
I've seen both
preview_database_iddatabase_preview_id in the code examples. Going between dev--localpreview__preview, absolutely can't debug when something isn't working correctly. 
Kdatabase_preview_id is definitely wrong.
UYeah all preview ids will start with preview_ 
Uwhere have you seen otherwise?
U
Mhi can I use worker for task like render csv file, it will tool time, just afraid limit of worker
SDoes somebody know of an article explaining a straightforward approach to securing workers (invocations only from other workers in the account or via an api key / client secret / credentials or the like)
Einvocations only from other workers in the accountYou can disable all public routes and use Service Bindings between Workers https://developers.cloudflare.com/workers/configuration/bindings/about-service-bindings/
Service bindings are an API that facilitate Worker-to-Worker communication via explicit bindings defined in your configuration.
DIs there an easy way to concat two ReadableStreams together into a single ReadableStream?
Dservice bindings for inter-Workers comms + Cloudflare Access for incoming requests from non-Workers
DHow could I use
FixedLengthStream to start at an offset of a ReadableStream? I'm trying to implement partial ranged reads.DHow can my Worker know it's own
CF-Worker header on outgoing requests?Upretty sure its just ur accounts workers.dev url so you can just manually set it but why would it need to know?
DI'm signing headers 
Uah I see makes sense
Cyou could have a transform rule modify request header and include it:
C(assuming this is a simple fetch worker, might get more complex if you're using service bindings. For Queue customer/cron/etc iirc its just always your workers.dev)
DHmm I wanted something that would work on any zone without configuration needed.
TAre workers suitable for high throughput websocket connection that lives for 1-5 minutes? Or is it too expensive?
JUsing cloudflare pages and deploying a nuxt website that uses cloudflare workers. I'm getting this error:
J
Jdoesn't seem to be an issue with my code as it works fine in development
Jsome rust function seems to be failing, but my app doesn't use rust
Jvery weird error
INitro (Nuxt's build/server system) uses Rust, I believe.
ISo probably a problem with whatever Nitro is doing in the build.
JPotentially
JRollup also uses rust
JI found this in source code for rollup
J
Jseems to be the error
Jbut I have absolutely no idea how to mitigate it from my source code
J
JI think the issue might be specific to cloudflare. When I run
npx nuxt build on my machine, it works.JNevermind
Jnpx nuxi build --preset=cloudflare_pages fails on my machineJfound the issue - it was in one of my libraries
VHow many routes are limited for workers? I have a webshop where i need to change SEO of a lot of urls 1000+
Is
Sorry this might be a stupid question.
Is
*.domainname/* considered one route? Or will each url targetted be one route?Sorry this might be a stupid question.
K1,000 routes per zone, and
*.domainname/* is a single route.K
VThank you! How much can workers that are run on whole domain decrease page speed ( the workers are pretty simple, like changing H1 to H3?
Can i avoid sending requests to static files?
Can i avoid sending requests to static files?
Dif you have static files, I recommend using Cloudflare Pages + Workers, if you don't want to pay for a Worker on the static file requests.
https://www.ai.moda/en/blog/do-not-use-custom-domains-for-workers <- this is how my team sets up Workers to play nice with Pages for static files
you can see how it looks in action at https://auth.ai.moda/pages/v1.0.0/login
^ we don't pay for any of the requests except for ones to
https://www.ai.moda/en/blog/do-not-use-custom-domains-for-workers <- this is how my team sets up Workers to play nice with Pages for static files
you can see how it looks in action at https://auth.ai.moda/pages/v1.0.0/login
^ we don't pay for any of the requests except for ones to
/api/v0.0.1/*ai.moda
Workers costs money, Pages are free on every request. You can't use a
SSO for ai.moda.
DI recommend versioning your Workers' routes for things you will have to maintain compatibility with long-term. That way if you want to refactor/rewrite your Worker in the future, you don't have to be scared about breaking things in production for existing users on the older Workers.
II'd also just add that Workers on the whole domain actually increase the startup time of the Worker because of this optimization: https://blog.cloudflare.com/eliminating-cold-starts-with-cloudflare-workers
KCloudflare does, since they control the end which is the Worker
KIf you mean you're encrypting stuff yourself, i.e PGP, then theoretically anything your Worker can do then Cloudflare could do.