SHey!
I'm trying to make old/outdated assets from previous deployments available for some time to keep the prior deployment of my React App workable.
I use
How I can handle that and keep old assets links available?
I'm trying to make old/outdated assets from previous deployments available for some time to keep the prior deployment of my React App workable.
I use
--old-asset-ttl for that and it keeps assets in KV, but seems links to that assets disapeare form __STATIC_CONTENT_MANIFEST (More details workers-and-pages-helpOld assets availability with `--old-asset-ttl`) How I can handle that and keep old assets links available?
JWere you able to figure this out?
Ano still trying
KI'm trying to use cloudflare tunnels to forward traffic to a localhost wrangler project. Works fine.
What doesn't seem to work is the request received by wrangler doesn't include the host header as defined in the tunnel config. Any solution?
What doesn't seem to work is the request received by wrangler doesn't include the host header as defined in the tunnel config. Any solution?
CTry setting the HTTP Host Header option for the tunnel. It will be under the public hostname
KYes, it is set. If I load the tunnel direct in chrome I can see the headers in the response (including custom headers defined via rules).
But when logging the request object received by wrangler, none of those headers are present
But when logging the request object received by wrangler, none of those headers are present
KThis is wrangler dev btw
Jhow set wrangler connect server with vpn proxy？ths big god。
PEither:
- run
for both worker projects orwrangler dev - include the second worker as a new WorkerEntrypoint in the same project (see demo project)
DI am using "wrangler pages dev" for building a simple Pages site (static html). I am getting errors from my browser due to the css file being served back with Content-Type: text/html instead of text/css. I see a few similar issues from 1-2 years ago, but not many, and no fixes. I also don't think I've had this issue with previous Pages developments. Any suggestions?
JThis would be how I would essentially do it
JSo besides the running multiple workers with Wrangler, the communicating between Workers can be done with Service bindings https://developers.cloudflare.com/workers/wrangler/configuration/#service-bindings
Ohey there, just wanted to ask if there was an eta on dynamic bindings? i would really like to use them for this one project because they would make my life just so much easier
KIs there anyway to get wrangler to work with localhost self signed certificates. This is a common issue with wrangler that has had no resolution since wrangler 3 was released. It's only a problem with wrangler.
DWhat's the latest compatibility date?
Dperfect 
RHello!
Having an issue trying to set up routes in wrangler.toml
I want to set both the custom domain and also the wildcard routes but I can't
Example of what I'm seeking:
What is the correct syntax ? The documentation doesn't mention both use cases together (custom domain and wildcard on subdomains); but the only way is to manually edit on the dashboard it seems ?
Having an issue trying to set up routes in wrangler.toml
I want to set both the custom domain and also the wildcard routes but I can't
Example of what I'm seeking:
What is the correct syntax ? The documentation doesn't mention both use cases together (custom domain and wildcard on subdomains); but the only way is to manually edit on the dashboard it seems ?
ACan a D1 binding be set up in a wrangler.toml file to take a local value for the
database_id.preview.vars and in the prod environment from a secret? The docs don't make it particularly clear if or how I might do that - or even how to use vars to be referenced with wrangler.toml
KNope, but IDs aren't secrets anyways.
AOkay, so there's no harm in the UUID of a prod DB being exposed in a repo - since it would presumably require credentials to even find out anything about it?
KYep
Aok, ta.
AHow can I find the db id of D1, deployed locally? I want to access it via drizzle studio, it asks them to be specified in .env , but I don’t have access to config variables of my local D1 database
RRecenlty getting : [ERROR] There was an access violation in the runtime. when running
npx wrangler pages dev ./dist
Sshould I add the wrangler file in gitignore if I want to make it public?
(ofc without any secret values in [vars])
or is it okay if it was public?
(ofc without any secret values in [vars])
or is it okay if it was public?
HAll of your wrangler config is safe to make public, as long as you do your dilingence with not putting secrets in it(as you noted)
Sthank you for the confirmation!
RWrangler trusted HTTPS?
wrangler dev --local-protocol https
Does not create a trusted certificate… easiest way to do it? I saw the key and cert flags for the dev command… can I use Cloudflare services to create a cert and key ?
wrangler dev --local-protocol https
Does not create a trusted certificate… easiest way to do it? I saw the key and cert flags for the dev command… can I use Cloudflare services to create a cert and key ?
ITailscale
ZI'm using wrangler+static assets+remix (classic compiler mode), and am running into this problem:
Anyone know what's going on here? I pushed a sample app to https://github.com/zwily/remix-wrangler-much-restarting with the config. You just
I filed a bug https://github.com/cloudflare/workers-sdk/issues/6865
- I edit a file
- remix compiler rebuilds, and places new files into
public/build - wrangler then does a reload for each new/updated file in
public/build, so it takes a long time and my window is full of this:
Anyone know what's going on here? I pushed a sample app to https://github.com/zwily/remix-wrangler-much-restarting with the config. You just
npm run devapp/routes/_index.tsx to see all the restarting action.I filed a bug https://github.com/cloudflare/workers-sdk/issues/6865
GitHub
Contribute to zwily/remix-wrangler-much-restarting development by creating an account on GitHub.
GitHub
Which Cloudflare product(s) does this pertain to? Wrangler What version(s) of the tool(s) are you using? 3.78.12 [Wrangler] What version of Node are you using? 18.18.2 What operating system and ver...
ZGitHub
What this PR solves / how to test
When files change in the assets directory, wrangler was reloading the app for every file. When the assets are the result of a build (like with the remix compiler, ...
When files change in the assets directory, wrangler was reloading the app for every file. When the assets are the result of a build (like with the remix compiler, ...
Wthanks so much for this! making sure this gets in:MeowHeartCloudflare:
FI'm trying to understand if there are any breaking changes between wrangler versions. Is there an easy way to do that? I'm trying to upgrade from 3.57.0 to latest, but want to confirm that this would be safe. Any help/ideas?
JFeature request (not sure if this is the right place for this):
- It would be nice if building rust using the workers build just worked (instead of having to install rust manually)
- It would be also be convenient (time saving of minutes) if the build supported some form of build caching for rust builds
�I'm encountering a weird issue, I got a monorepo repo structure that looks like this
you see the apps and some packages need each other to function and also it's designed that kv, d1, r2.. etc is remote, but since the miniflare instance/ .wrangler is made in each project separately it breaks the whole functionality in local development, how can I make all apps use the same .wrangler/miniflare instace instead of creating one separately each time
you see the apps and some packages need each other to function and also it's designed that kv, d1, r2.. etc is remote, but since the miniflare instance/ .wrangler is made in each project separately it breaks the whole functionality in local development, how can I make all apps use the same .wrangler/miniflare instace instead of creating one separately each time
Zi find myself bouncing between accounts using the wrangler cli often. does anyone have any nifty tools to make that easier? (i'd love it if wrangler let us log into multiple accounts, and use the correct one based on the account_id specified in
wrangler.toml
MThis would be a tool that I'd make sure to include in my stack. Currently, I'm containerising projects/accounts.
KYou could probably make some tool to swap out
~/.wrangler/config/default.tomlMThis could be a good start https://developers.cloudflare.com/workers/wrangler/system-environment-variables/
Cloudflare Docs
Local environment variables that can change Wrangler's behavior.
ZSo i guess i could just sprinkle .env files around? And hope i don’t accidentally commit any to git? 
RIs it possible to use
npx wrangler pages dev ./dist but not from the ./dist folder b ut from the dev source? i.e. from npm run dev?
HNo, that was a thing with —proxy, but it was removed due to being a bit finnicky
HThe recommendation is to use a framework that supports bindings in dev mode
RI am still struggling with api keys not supporting lockdown to either a specific worker or pages project as well as production and preview. Is this going to be fixed? It feels like I have asked several times and it seemed other people needed it as well. I am currently unable to invite other developers to help with workers or pages projects unless I use github ci, but when using github ci, it's kind of dangerous as well; if someone decides to change the github action to deploy on a different cloudflare project they can easily overwrite or deploy things they should not, especially on preview branches.
AI dont know how to test...
Wangler dev work but not for DO with rpc.
Wrangler dev --remote works but not for static assets...
How do I combine both or test my code haha
Wangler dev work but not for DO with rpc.
Wrangler dev --remote works but not for static assets...
How do I combine both or test my code haha
