https://discord.com/channels/595317990191398933/1274809595390591017

M

mihaaai•8/18/24, 7:26 PM

Already tried that but didn't work, now I just solved it by solving another problem

I had a custom esbuild command for wrangler that I set a long time ago for some integration reason, by using the

wrangler deploy --dry-run --outdir=path/to/build

wrangler deploy --dry-run --outdir=path/to/build

wrangler deploy --dry-run --outdir=path/to/build

wrangler deploy --dry-run --outdir=path/to/build for the build, the deploy went well, and the library is working like a charm!

Thanks for the prompt help!

Vvamtic:https://discord.com/channels/595317990191398933/1274809595390591017

I

Isaac McFadyen•8/18/24, 7:27 PM

Please do not crosspost your questions. You were already warned once.

A

ahwelgemoed•8/19/24, 1:36 PM

Hey All - I was working today on a Worker that listens to a Event Notification on a "put" of a file to R2. I sank some time in trying to figure out why uploading a file did not trigger my queue. After some time I realised that all was working as it should. Seems like R2 triggers don't work locally (while developing)

I can confirm that they do work when deployed. Is this a know limitation? Or did I miss something obvious in the docs?

L

lj•8/22/24, 1:30 AM

Is there a way

wrangler pages dev [dist]

wrangler pages dev [dist]

wrangler pages dev [dist]

wrangler pages dev [dist] can proxy the static asset that hosted by vite?

L

lj•8/22/24, 2:54 AM

why

--proxy                                      The port to proxy (where the static assets are served)  [deprecated] [number]

--proxy                                      The port to proxy (where the static assets are served)  [deprecated] [number]

--proxy                                      The port to proxy (where the static assets are served)  [deprecated] [number]

--proxy                                      The port to proxy (where the static assets are served)  [deprecated] [number]

and

  command    The proxy command to run  [deprecated]  [string]

command The proxy command to run [deprecated] [string]

  command    The proxy command to run  [deprecated]  [string]

command The proxy command to run [deprecated] [string]

L

lj•8/22/24, 3:00 AM

deprecated

H

Hello, I’m Allie!•8/22/24, 7:25 AM

@Hard@Work | R2

O

oof2win2•8/22/24, 7:47 AM

are there plans to support sharing resources such as r2 or d1 on local development? say i bind to the same d1 by ID so it would make sense if wrangler communicated to connect to the same sqlite database

Ooof2win2 are there plans to support sharing resources such as r2 or d1 on local developme...

L

lj•8/22/24, 7:49 AM

https://developers.cloudflare.com/pages/functions/bindings/#interact-with-your-d1-databases-locally

Cloudflare Docs

Bindings | Cloudflare Pages docs

A binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions with Cloudflare resources like KV, Durable Objects, R2, and D1. You can set bindings for both production and preview environments.

O

oof2win2•8/22/24, 7:53 AM

i have all of those in a wrangler.toml already from which it reads so thats fine

O

oof2win2•8/22/24, 7:53 AM

i mean when i have two separate workers bound to the same d1 instance, they should also be bound to the same sqlite instance locally

Ooof2win2 i mean when i have two separate workers bound to the same d1 instance, they shou...

H

Hello, I’m Allie!•8/22/24, 8:00 AM

If you

—persist-to

—persist-to

—persist-to

—persist-to the same directory for both Workers, they will share data

L

lj•8/22/24, 8:04 AM

I'm a single developer have a SPA web app. I just want to save some todo by Functions. It's hard that develop SPA by wrangler pages dev

O

oof2win2•8/22/24, 8:05 AM

ooh thanks!

L

lj•8/22/24, 8:05 AM

Develop the SPA by Vite is a good way. How can I combine them together?

Llj I'm a single developer have a SPA web app. I just want to save some todo by Func...

H

Hello, I’m Allie!•8/22/24, 8:05 AM

Frameworks can add support for Bindings via getPlatformProxy, which is what we now recommend

HHello, I’m Allie!Frameworks can add support for Bindings via getPlatformProxy, which is what we n...

L

lj•8/22/24, 8:06 AM

I notice that. But what should i do? getPlatformProxy used in functions or my SPA?

L

lj•8/22/24, 8:07 AM

Or should I wait the frameworks support that?

Llj I notice that. But what should i do? getPlatformProxy used in functions or my SP...

H

Hello, I’m Allie!•8/22/24, 8:08 AM

In your Framework. Then when you run the build command, it builds your Functions for you

O

oof2win2•8/22/24, 8:09 AM

can i somehow set flags in wrangler toml or are they commandline only? i remember seeing a

.env

.env

file being used for something for wrangler itself

O

oof2win2•8/22/24, 8:10 AM

nvm it isnt an option

A

Arthur Fiorette•8/23/24, 3:36 AM

Hello. I bet i'm the 10000th person to ask this but i can't figure a way to solve this problem:

I'm running my local worker with

wrangler dev --port 8788 --local --ip 0.0.0.0

wrangler dev --port 8788 --local --ip 0.0.0.0

wrangler dev --port 8788 --local --ip 0.0.0.0

wrangler dev --port 8788 --local --ip 0.0.0.0 and a local proxy for proxy

*.domain.local

*.domain.local

*.domain.local

*.domain.local to the worker. However, on every request, the

Host

Host

Host

Host header is being set to my

routes[0].pattern

routes[0].pattern

routes[0].pattern

routes[0].pattern defined in

wrangler.toml

wrangler.toml

... How can i fix that??

If I just spin up a local nodejs server to print the request headers, i see that my proxy is forwarding the correct header, but the wrangler itself is changing it back to the routes...

I saw https://github.com/cloudflare/wrangler-legacy/issues/2319 but

--local

--local

did not solved this issue...

If i remove

routes

routes

from

wrangler.toml

wrangler.toml

, the host header isn't overwritten and work as expected.

I

ian•8/24/24, 12:43 AM

Has anyone gotten sentry sourcemap uploads working with wrangler build?

A

AISyntax•8/25/24, 10:40 PM

not sure how I broke this, but I started getting this error while following the learn cloudflare worker beginner youtube tutorial. I've tried npm install after deleting node_modules and package-lock. not sure if I should back up to a working state and try again or what.

A

AISyntax•8/25/24, 10:40 PM

A

AISyntax•8/25/24, 10:49 PM

the error log is telling me it cant find a couple files, ".env" and ".dev.vars"

A

AISyntax•8/25/24, 10:50 PM

any help would be appreciated!

AISyntax_Discord_Wrangler_Dev.log2.5KB

A

AISyntax•8/25/24, 10:57 PM

i guess, never mind? I just commented and uncommented the AI binding in the toml file and it started working again. okey dokey thanks!

A

AISyntax•8/25/24, 11:11 PM

@Skye | Project

thanks for mentioning that! Even after my last post, I ended up back at the same problem. I just removed that wrapping and I am back on track with learning again. Thanks!

M

Mitya•8/26/24, 9:57 AM

Just a thought, but it would be neat if Wrangler had a command to switch between two logged-in accounts. I use CF for both work and personal, and it's a little laborious to to have to keep logging out of one account and into another, sometimes multiple times a day. Could this be a feature, or is there some other way to handle this?

MMitya Just a thought, but it would be neat if Wrangler had a command to switch between...

H

Hard@Work•8/26/24, 10:14 AM

You can use API tokens, or give one account access to the other

H

Hard@Work•8/26/24, 10:14 AM

Neither are entirely ideal, but that is what is there atm.

HHard@Work You can use API tokens, or give one account access to the other

M

Mitya•8/26/24, 3:50 PM

"... or give one account access to the other"

My personal account has access to my work account, but as I understand it I'd still need to logout of one account (in the browser and in Wrangler) and into the other account when I need to run wrangler commands, to ensure it's communicating with the right account, no?

MMitya _"... or give one account access to the other"_ - My personal account has access...

H

Hard@Work•8/26/24, 3:56 PM

You can add the account ID to your

wrangler

wrangler

config, then it should

fail if you aren't set up with perms for the right account

HHard@Work You can add the account ID to your `wrangler` config, then it should™️ fail if y...

M

Mitya•8/26/24, 5:52 PM

Do you mean add a reference to account ID within

wrangler.toml

wrangler.toml

, and then Wrangler will run any commands against one CF account or the other, depending on the account ID found in the project's TOML?

M

Mitya•8/26/24, 5:52 PM

If so, would that be as a top-level (i.e. non-inherited) variable?

Original message was deleted

H

Hello, I’m Allie!•8/27/24, 7:22 AM

For wrangler?

C

captain•8/29/24, 7:57 PM

has anybody had an issue and know how to fix a scenario where they went to a coffee shop, but wifi wasn't connected fully, then when they tried to deploy using wrangler without being fully connected, then failed. Then when connected again for some reason the tab http://cloudflareportal.com/test keeps opening ever 60 or 180 seconds...? its maddening

C

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

anybody...

Ccaptain has anybody had an issue and know how to fix a scenario where they went to a cof...

I

Isaac McFadyen•8/29/24, 8:27 PM

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

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

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

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

https://discord.com/channels/595317990191398933/1274809595390591017

Similar Threads