Have you tried a full system reboot?

C

captain•8/29/24, 9:29 PM

no

IIsaac McFadyen Have you tried a full system reboot?

C

captain•8/29/24, 9:29 PM

ideally there is a command i could do as I have a lot of open files and work in various programs

L

LimesKey•8/30/24, 5:29 PM

I'm running Wrangler with Rust and trying to use the TOTP crate but I'm getting this,

  (error) panicked at library/std/src/sys/pal/wasm/../unsupported/time.rs:31:9:
time not implemented on this platform

  (error) panicked at library/std/src/sys/pal/wasm/../unsupported/time.rs:31:9:
time not implemented on this platform

  (error) panicked at library/std/src/sys/pal/wasm/../unsupported/time.rs:31:9:
time not implemented on this platform

  (error) panicked at library/std/src/sys/pal/wasm/../unsupported/time.rs:31:9:
time not implemented on this platform

L

LimesKey•8/30/24, 5:35 PM

ah I got it fixed, I had to use

use wasm_timer::{SystemTime, UNIX_EPOCH};

use wasm_timer::{SystemTime, UNIX_EPOCH};

use wasm_timer::{SystemTime, UNIX_EPOCH};

use wasm_timer::{SystemTime, UNIX_EPOCH}; and do something like this,

let token = totp.generate(wasm_timer::SystemTime::now().duration_since(UNIX_EPOCH).unwrap().as_secs());

let token = totp.generate(wasm_timer::SystemTime::now().duration_since(UNIX_EPOCH).unwrap().as_secs());

let token = totp.generate(wasm_timer::SystemTime::now().duration_since(UNIX_EPOCH).unwrap().as_secs());

let token = totp.generate(wasm_timer::SystemTime::now().duration_since(UNIX_EPOCH).unwrap().as_secs());

J

Jando•8/31/24, 12:13 AM

Does anyone know if

npm create cloudflare@latest

npm create cloudflare@latest

npm create cloudflare@latest

npm create cloudflare@latest

The new alis for wrangler init has the --yes option? I wanted to run this in a bash script

J

Jando•8/31/24, 12:16 AM

-y seems to just init a default cloudflare worker

E

Elyo•8/31/24, 11:00 AM

Hi guys!
I feel a bit confused with

wrangler.toml

wrangler.toml

wrangler.toml

wrangler.toml I would like to create 3 environments with different secret within the same project. Basically, staging / UAT / Prod.

Does those 3 workers can be created from the same wrangler file?
I want to have 3 different domain.
I already have a custom domain for my current worker, but I would like to extend to 2 more env.

[env.production]
route =  [
  { pattern = "prod.mydomain.com", custom_domain = true }
]

[env.uat]
route =  [
  { pattern = "uat.mydomain.com", custom_domain = true }
]

[env.staging]
route =  [
  { pattern = "staging.mydomain.com", custom_domain = true }
]

[env.production]
route =  [
  { pattern = "prod.mydomain.com", custom_domain = true }
]

[env.uat]
route =  [
  { pattern = "uat.mydomain.com", custom_domain = true }
]

[env.staging]
route =  [
  { pattern = "staging.mydomain.com", custom_domain = true }
]

[env.production]
route =  [
  { pattern = "prod.mydomain.com", custom_domain = true }
]

[env.uat]
route =  [
  { pattern = "uat.mydomain.com", custom_domain = true }
]

[env.staging]
route =  [
  { pattern = "staging.mydomain.com", custom_domain = true }
]

[env.production]
route =  [
  { pattern = "prod.mydomain.com", custom_domain = true }
]

[env.uat]
route =  [
  { pattern = "uat.mydomain.com", custom_domain = true }
]

[env.staging]
route =  [
  { pattern = "staging.mydomain.com", custom_domain = true }
]

And then run e.g.

wrangler run deploy --env uat

wrangler run deploy --env uat

wrangler run deploy --env uat

wrangler run deploy --env uat for uat

Is that the best practice?

J

James•8/31/24, 9:29 PM

Yep that's exactly how I'd handle it

E

Elyo•9/1/24, 6:52 AM

Thanks a lot @James !

J

jason•9/2/24, 5:28 AM

For my Pages project, the following

wrangler.toml

wrangler.toml

wrangler.toml

wrangler.toml allows migration commands to work against 1.) remote preview DB & 2.) production DB.

[[d1_databases]]
binding = "D1"
database_name = "mysite-prod"
database_id = "<productionUUID>"
preview_database_id = "<previewUUID>" # this is different
migrations_dir = "./src/lib/server/database/migrations"

[[d1_databases]]
binding = "D1"
database_name = "mysite-prod"
database_id = "<productionUUID>"
preview_database_id = "<previewUUID>" # this is different
migrations_dir = "./src/lib/server/database/migrations"

[[d1_databases]]
binding = "D1"
database_name = "mysite-prod"
database_id = "<productionUUID>"
preview_database_id = "<previewUUID>" # this is different
migrations_dir = "./src/lib/server/database/migrations"

[[d1_databases]]
binding = "D1"
database_name = "mysite-prod"
database_id = "<productionUUID>"
preview_database_id = "<previewUUID>" # this is different
migrations_dir = "./src/lib/server/database/migrations"

The following allows migrations against 1.) local DB and 2.) production DB.

[[d1_databases]]
binding = "D1"
database_name = "mysite-prod"
database_id = "<productionUUID>"
preview_database_id = "D1"     # this is different.
migrations_dir = "./src/lib/server/database/migrations"

[[d1_databases]]
binding = "D1"
database_name = "mysite-prod"
database_id = "<productionUUID>"
preview_database_id = "D1"     # this is different.
migrations_dir = "./src/lib/server/database/migrations"

[[d1_databases]]
binding = "D1"
database_name = "mysite-prod"
database_id = "<productionUUID>"
preview_database_id = "D1"     # this is different.
migrations_dir = "./src/lib/server/database/migrations"

[[d1_databases]]
binding = "D1"
database_name = "mysite-prod"
database_id = "<productionUUID>"
preview_database_id = "D1"     # this is different.
migrations_dir = "./src/lib/server/database/migrations"

I found this quite frustrating b/c the naming is conflated:
I.e. this uses

preview_database_id

preview_database_id

preview_database_id

preview_database_id for local development, but KV has

preview_id

preview_id

preview_id

preview_id & R2 has

preview_database_id

preview_database_id

preview_database_id

preview_database_id which are for remote preview resources.

This took hours to figure out why my migrations were not working predictably, across my local/preview/production DBs.

I hope this can be improved/changed so that D1 is consistent. IMO, the local D1 should simply use the binding name and

preview_database_id = "<previewUUID>"

preview_database_id = "<previewUUID>"

preview_database_id = "<previewUUID>"

preview_database_id = "<previewUUID>" should always and only be consistently used for the remote preview UUID.

M

micah•9/2/24, 5:46 AM

Is there a way to use snippets with wrangler

V

Vero•9/2/24, 3:40 PM

See you in September 2, 2024:Wrangler:
https://discord.gg/cloudflaredev?event=1270670702990852159

VVero See you in <t:1725292800:R>:Wrangler: https://discord.gg/cloudflaredev?event=12...

V

Vero•9/2/24, 5:11 PM

Wrangler_Office_Hours_-_September_2024.mp328.92MB

VVero Click to see attachment

A

Aditya Mathur•9/2/24, 5:19 PM

Is service like firebase ever gonna be supported with workers?

S

scruffy•9/3/24, 9:45 AM

Howdy! Am experimenting with

--x-registry

--x-registry

--x-registry

--x-registry in a pnpm monorepo and running into an issue with service bindings...

pnpm run -r dev

pnpm run -r dev

pnpm run -r dev

pnpm run -r dev works fine until I add a service binding. Using

sleep 1 && wrangler dev

sleep 1 && wrangler dev

sleep 1 && wrangler dev

sleep 1 && wrangler dev in worker A (with the binding) gives enough time for the bound worker B to arrive and be ready to be bound to by A, so everything works. Is there a simpler/unhacky way of working locally with service bindings in a monorepo? Fingers crossed and thanks in advance for any help

AArthur Fiorette Hello. I bet i'm the 10000th person to ask this but i can't figure a way to solv...

S

scruffy•9/3/24, 11:02 AM

ymmv, but i handled this by making the routes definition inside

env.production

env.production

env.production

env.production (so it's not available locally)

AAditya Mathur Is service like firebase ever gonna be supported with workers?

V

Vero•9/3/24, 1:49 PM

not planned yet afaik

L

Leo Hoang•9/4/24, 9:31 AM

Hi guys!
I'm running wrangler login when use cloudflare pages but it return 400 bad request error , is there anyway to fix

W

Walshy•9/4/24, 11:04 AM

Delete your cookies for dash.cloudflare.com and try again

WWalshy Delete your cookies for dash.cloudflare.com and try again

L

Leo Hoang•9/4/24, 11:25 AM

Thanks a lot @Walshy

J

James Eastham•9/6/24, 12:36 PM

Hey everyone, is there a way to run

wrangler dev

wrangler dev

in the background? Kind of like passing the

-d

-d

-d

-d flag to Docker? I am specifically thinking for a CICD pipeline, where I might want to startup a local dev instance to test against before pushing my changes out to Cloudflare.

The only alternative I can think of is to run a deploy using a dev environment...

JJames Eastham Hey everyone, is there a way to run `wrangler dev` in the background? Kind of li...

H

Hard@Work•9/6/24, 12:37 PM

I would check out https://developers.cloudflare.com/workers/testing/

Cloudflare Docs

Testing | Cloudflare Workers docs

Review the tools available for testing and debugging Workers.

J

James Eastham•9/6/24, 12:41 PM

Oh, nice. Thanks for the link @Hard@Work | R2

I'm building with Rust at the moment, not Javascript. but I'll see if there's anything similar in the Cloudflare/Rust tooling

F

flaan4me•9/10/24, 5:34 PM

Can I install wrangler on android

K

kaelys.js•9/10/24, 10:21 PM

How do I get localhost tls peer cert not trusted to work?

Latest wrangler / macOS.

I’ve tried all the solutions in the git repo and tried mkcert but nothing works.

K

kaelys.js•9/11/24, 12:52 AM

(Judging by a discord/git/stack overflow search, this is an issue that’s unresolved since wrangler 3 was released).

JJames Eastham Hey everyone, is there a way to run `wrangler dev` in the background? Kind of li...

J

JacobMGEvans•9/13/24, 6:24 AM

Wrangler can run on CI/CDs especially GH Actions, there is even a prebuilt Action for it. You can just run it as a script in the CI/CD

A

A•9/14/24, 7:15 PM

Getting this how Can I fix this?

S

Serhii Bilonoh•9/16/24, 7:36 AM

Hey!
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

--old-asset-ttl

--old-asset-ttl

--old-asset-ttl for that and it keeps assets in KV, but seems links to that assets disapeare form

__STATIC_CONTENT_MANIFEST

__STATIC_CONTENT_MANIFEST

__STATIC_CONTENT_MANIFEST

__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?

AA Getting this how Can I fix this?

J

JacobMGEvans•9/16/24, 8:33 PM

Were you able to figure this out?

JJacobMGEvans Were you able to figure this out?

A

A•9/17/24, 1:29 PM

no still trying

K

kaelys.js•9/17/24, 11:47 PM

I'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?

Kkaelys.js I'm trying to use cloudflare tunnels to forward traffic to a localhost wrangler ...

C

Cyb3r-Jak3•9/17/24, 11:51 PM

Try setting the HTTP Host Header option for the tunnel. It will be under the public hostname

K

kaelys.js•9/17/24, 11:53 PM

Yes, 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

K

kaelys.js•9/17/24, 11:59 PM

This is wrangler dev btw

J

johny•9/19/24, 12:49 AM

how set wrangler connect server with vpn proxy？ths big god。

Ppunkmonk Or maybe a better question, how do you run multiple workers in local dev environ...

P

Payello•9/19/24, 11:50 AM

Either:

run
```
wrangler dev
```
```
wrangler dev
```
for both worker projects or
include the second worker as a new WorkerEntrypoint in the same project (see demo project)

D

Devon•9/19/24, 5:13 PM

I 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?

PPayello Either: - run `wrangler dev` for both worker projects or - include the second wo...

J

JacobMGEvans•9/20/24, 2:30 AM

This would be how I would essentially do it

Ppunkmonk Or maybe a better question, how do you run multiple workers in local dev environ...

J

JacobMGEvans•9/20/24, 2:32 AM

So 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

O

oof2win2•9/23/24, 3:31 AM

hey 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

K

kaelys.js•9/23/24, 11:51 PM

Is 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.

D

Dr. Software•9/24/24, 3:39 PM

What's the latest compatibility date?

D

Dr. Software•9/24/24, 3:46 PM

perfect

R

rufi•9/24/24, 6:37 PM

Hello!

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:

# wrangler.toml
[env.production]
vars = { ENVIRONMENT = "production" }
routes = [
  { pattern = "sub.mysite.io/*", zone_name = "mysite.io" },
  { pattern = "sub.mysite.io", zone_name = "mysite.io", custom_domain = true },
]

# wrangler.toml
[env.production]
vars = { ENVIRONMENT = "production" }
routes = [
  { pattern = "sub.mysite.io/*", zone_name = "mysite.io" },
  { pattern = "sub.mysite.io", zone_name = "mysite.io", custom_domain = true },
]

# wrangler.toml
[env.production]
vars = { ENVIRONMENT = "production" }
routes = [
  { pattern = "sub.mysite.io/*", zone_name = "mysite.io" },
  { pattern = "sub.mysite.io", zone_name = "mysite.io", custom_domain = true },
]

# wrangler.toml
[env.production]
vars = { ENVIRONMENT = "production" }
routes = [
  { pattern = "sub.mysite.io/*", zone_name = "mysite.io" },
  { pattern = "sub.mysite.io", zone_name = "mysite.io", custom_domain = true },
]

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 ?

A

akashra•9/25/24, 1:31 AM

Can a D1 binding be set up in a wrangler.toml file to take a local value for the

database_id

database_id

database_id

database_id for pages development from

.preview.vars

.preview.vars

.preview.vars

.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

Have you tried a full system reboot?

Similar Threads

Similar Threads

Similar Threads