YI just reread the docs and saw that deployment of python apps doesn't work, i have a fastapi app, so let me wait
Yhow soon do you think we will get python deployments? in 3 months? do js backends already work?
WSee https://discord.com/channels/595317990191398933/1224715939581530112/1332045636983459851 for Python package support
and yes, js works
and yes, js works
JHi, I've run into an issue for a new project I just started working on, that I've run into before (but the solution I implemented wasn't exactly 'ideal'), and I was wondering if there is an official workaround now. Basically if I'm running a worker locally using
wrangler dev*.example.comhttp://something.localhost:8787) the request URL gets rewritten to http://example.com - no matter what the subdomain is. Effectively making it impossible for me to use subdomains locally with
. Is there any way of disabling this functionality locally? I totally get why it's there (for non-wildcard routes) but it causes issues with subdomains.wrangler dev
JAre the wrangler.toml validators exported/published anywhere for third party libraries to use?
JI'm not sure if there's any exposed validators code-wise, but they do publish a
config-schema.jsonwrangler
HIIRC too there is some kind of shebang that you can put at the top of the toml file to have it validated. I think it works with the
Even Better TOML#: schema ./node_modules/wrangler/config-schema.json
VIn local dev mode with wrangler, is there a way to run a worker and a durable object.
- worker is the main site
- durable is a websocket server under /path
This setup works find in production, where I can use worker routes. Is there something similar for local dev? (so it looks like both are under localhost:3000 and I can dev like I prod?
HNot entirely sure I understand what you mean? You can just have the Worker forward requests on
/path
AI am on v3.109.1 and whenever I try to deploy with wrangler deploy, getting this error:
Why can't I deploy with CLOUDFLARE_API_TOKEN ? It used to work fine with older version!
You are logged in with an API Token. Unset the CLOUDFLARE_API_TOKEN in the environment to log in via OAuth.Why can't I deploy with CLOUDFLARE_API_TOKEN ? It used to work fine with older version!
Mhi team ! How can we handle very sensetive data like crypto wallet keys in backend using workers ? what is the recommended approach?
VOn localhost, where I am developing. I already do that in prod between workers, I need something better on localhost for multiple workers running at the same time
HOh, you meant a DO within one Worker and a separate Worker, on the same port?
H
VIs it possible to connect two workers on localhost through the binding mechanisms? (This subpath stuff is going away eventually, can move that work forward)
HHm… that might work?
VI recall (maybe) that it was not supported yet, but I was a bit early in my journey to hang the details on prior experience. For now, for the feature I'm working on, http fetch is going to be fine, just have to make the websocket host configurable for dev vs prod.
Actually, I did want the websocket worker to share the D1 & KV with the webapp worker. Is this possible in prod & local dev? (prod seems like an easy yes? while dev seems like it may be an issue because they are in different dirs and running in different wrangler setups?
Actually, I did want the websocket worker to share the D1 & KV with the webapp worker. Is this possible in prod & local dev? (prod seems like an easy yes? while dev seems like it may be an issue because they are in different dirs and running in different wrangler setups?
VMaybe using a remote preview environment is the way to handle this in local dev mode?
HYou should be able to point both to the same directory with
—persist-toI'll give it a try a bit later and report back, would be helpful to expand the wording and examples to cover multi-worker setups on this page: https://developers.cloudflare.com/workers/local-development/
Cis it possible to deploy a workers without a browser to log in?
VIs there a way to support using wrangler with multiple accounts locally, so I don't have to oauth as a switch between projects I need to deploy?
(hoping that there is a similar answer to @custom's question, i.e. something like an API Key)
(hoping that there is a similar answer to @custom's question, i.e. something like an API Key)
CThat is exactly what I want
VI'm testing it out now
Vfyi, that page is out of date
Vok, got it working, needed ENV vars to be CLOUDFLARE_EMAIL and CLOUDFLARE_API_TOKEN
ぷI suspect it is a bug in wrangler.
I always get EOF with functions for local environment.
d1-database
When using the wrangler dev command, the server does not start and an EOF error occurs.
I always get EOF with functions for local environment.
d1-database
When using the wrangler dev command, the server does not start and an EOF error occurs.
ぷHono also get EOF for the dev command, but the deploy command is possible and works fine when checked in the browser after deployment.
GHi ! My company have an access to all the CF account of our clients. We have some bash scripts to do some tasks like "npx wrangler deploy". When we create a new project, without yet the node_modules/.mf/ directory, the CLI wrangler will ask us on which account to upload it.
The problem is it's not works inside a bash script ( SystemError [ERR_TTY_INIT_FAILED]: TTY initialization failed: uv_tty_init returned EINVAL )
I've search in the command parameters, I haven't found one to explicit choose the client account. May be there another solution ?
The problem is it's not works inside a bash script ( SystemError [ERR_TTY_INIT_FAILED]: TTY initialization failed: uv_tty_init returned EINVAL )
I've search in the command parameters, I haven't found one to explicit choose the client account. May be there another solution ?
Hhttps://developers.cloudflare.com/workers/wrangler/configuration/#inheritable-keys
This is the ID of the account associated with your zone. You might have more than one account, so make sure to use the ID of the account associated with the zone/route you provide, if you provide one. It can also be specified through theenvironment variable.CLOUDFLARE_ACCOUNT_ID
GThank you for your help (again!)
But it's not works in the case of « CLOUDFLARE_ACCOUNT_ID=xxxx npm create cloudflare@latest -- $PROJECT --experimental (...) » and « CLOUDFLARE_ACCOUNT_ID=xxxx npx create-cloudflare -- $PROJECT --experimental (...) »
I still got the error ╰ ERROR SystemError [ERR_TTY_INIT_FAILED]: TTY initialization failed: uv_tty_init returned EINVAL (invalid argument)
But it's not works in the case of « CLOUDFLARE_ACCOUNT_ID=xxxx npm create cloudflare@latest -- $PROJECT --experimental (...) » and « CLOUDFLARE_ACCOUNT_ID=xxxx npx create-cloudflare -- $PROJECT --experimental (...) »
I still got the error ╰ ERROR SystemError [ERR_TTY_INIT_FAILED]: TTY initialization failed: uv_tty_init returned EINVAL (invalid argument)
GI'm using the account id of my client and it's the default static asset configuration created on the fly from create-cloudflare so I doesn't have any control of the config, excepted the CLI parameters or ENV vars
HIt should work for wrangler, but I don’t think c3 works without interactivity
HWhy not just create it once with c3, then push to git
Gfew years ago, before C3, if I remember correctly we could init a project from wrangler directly, I can try that if it's still supported in wrangler
HI believe that uses c3 now too
Gyep I've just read that in the doc ^^
GI'll do it in 2 steps, without automatic deploy, thank you for your help!
ぷI have created a Hello, World starter, but does anyone else get an EOF error when using the wrangler dev command at wrangler@3.109.2?
VIs it possible to run a TS script within the context of wrangler and my bindings? I'd like to write my D1 seeding code in a real programming language rather than raw SQL
BWhy is wrangler.jsonc now supported, and seemingly the default option (docs default to this, and this file gets generated)? For an app i work on, I added support for yaml files instead of just json/jsonc (for backwards compatibility) and recommend everyone to use yaml because it minimises special characters (
I'm just curious. I tried to search for it and check the PR but didn't find an answer. Probably just some slight familiarity for most developers knowing json already? Or maybe it pairs up with Json Schema a bit better.
{}I'm just curious. I tried to search for it and check the PR but didn't find an answer. Probably just some slight familiarity for most developers knowing json already? Or maybe it pairs up with Json Schema a bit better.
HOne, as you pointed out, is JSON schemas. While there is a way to validate TOML with a schema, I don’t think it is an official standard. In addition, quite a few people had issues with TOML inheritance, and being that most Workers are written in JS, most devs building on Workers are more familiar with JSON
HThough note above is a best guess, as I am not on the Developer Productivity Team, which oversees wrangler, and would know what the official reasoning is
RHi guys, i'm new using wrangler and the cloudflare ecosystem. I want to know if there is a straightforward (non-manual) way to retrieve and update the IDs of resource bindings associated with another Cloudflare account in the wrangler config?
I mean, when i clone a repo with a wrangler config, and I want to deploy it in my account, i always must create and change manually the ids of resources?
I mean, when i clone a repo with a wrangler config, and I want to deploy it in my account, i always must create and change manually the ids of resources?
VCUE is the way :] schemas + config in a single language
JSONC is just another hack on a data format when what we really want is a proper config language
JSONC is just another hack on a data format when what we really want is a proper config language
FHi guys, this morning when trying to promote some of our Cloudflare Pages from our CI pipeline(s), they all failed with the following error:
Any ideaas? Thank you!
Any ideaas? Thank you!
FOK, I have re-run all the failed tasks and they all passed now - I just it might have been some transient issue.
BDoes wrangler need some kind of special flags to print stderr normally when stderr is a pipe? I'm not seeing any of the console.debug messages unless I spawn wrangler with stderr set to inherit. I've tried --log-level but that seems to be the workerd log level.
