I only use [[services]] in the wrangler.toml

TTilon I only use [[services]] in the wrangler.toml

T

TheSunSide•8/19/22, 9:28 PM

You need to define [miniflare.mounts] so your local env knows where to fetch those workers

T

TheSunSide•8/19/22, 9:28 PM

I'm using miniflare directly, but it should be similar

T

TilonOP•8/19/22, 9:29 PM

Thx, I will try that

T

TilonOP•8/19/22, 9:31 PM

Ignored: "miniflare":
Wrangler does not use configuration in the

miniflare

miniflare

miniflare

miniflare section. Unless you are using Miniflare
directly you can remove this section.

T

TilonOP•8/19/22, 9:32 PM

Too bad, looks like there is a difference between wrangler local and „pure“ miniflare

T

TheSunSide•8/19/22, 9:38 PM

▲ [WARNING] This worker is bound to live services: MAIL_FETCH (mail@local), LOGGER_SERVER (logger@local)

local worker: Error: ⎔ Service bindings are not yet supported in local mode.

T

TheSunSide•8/19/22, 9:38 PM

Might need to wait for wrangler to do it

T

TheSunSide•8/19/22, 9:38 PM

If you want true "local"

T

tacomilkshake•8/19/22, 9:42 PM

New Wrangler dev defaults to 0.0.0.0 so I added [dev] ip = '127.0.0.1' to wrangler.toml. wrangler dev doesn't use that config and remains at 0.0.0.0. Seems like a bug, ya?

Original message was deleted

T

tacomilkshake•8/19/22, 10:01 PM

https://github.com/cloudflare/wrangler2/issues/1714

T

tacomilkshake•8/19/22, 10:29 PM

Having another very weird issue with Wrangler dev on two devices (Mac + Ubuntu):

npx wrangler init my-worker
cd my-worker/
npx wrangler dev --ip 127.0.0.1

npx wrangler init my-worker
cd my-worker/
npx wrangler dev --ip 127.0.0.1

npx wrangler init my-worker
cd my-worker/
npx wrangler dev --ip 127.0.0.1

npx wrangler init my-worker
cd my-worker/
npx wrangler dev --ip 127.0.0.1

curl localhost:8787 works

npx wrangler init my-worker
cd my-worker/
npx wrangler secret put TEST
npx wrangler dev --ip 127.0.0.1

npx wrangler init my-worker
cd my-worker/
npx wrangler secret put TEST
npx wrangler dev --ip 127.0.0.1

npx wrangler init my-worker
cd my-worker/
npx wrangler secret put TEST
npx wrangler dev --ip 127.0.0.1

npx wrangler init my-worker
cd my-worker/
npx wrangler secret put TEST
npx wrangler dev --ip 127.0.0.1

curl localhost:8787 no longer works -- it just hangs.

Basically, adding an environment variable to any new worker breaks wrangler dev.

Original message was deleted

T

tacomilkshake•8/19/22, 10:30 PM

Ah ha, thanks! Kinda glad it's not just me. I was losing my mind!

Original message was deleted

T

tacomilkshake•8/19/22, 10:31 PM

ooh, didn't know that. thanks!

K

kian•8/19/22, 10:37 PM

hidden deep under the config code dump https://developers.cloudflare.com/workers/wrangler/configuration/#local-environments

K

kian•8/19/22, 10:37 PM

K

kian•8/19/22, 10:37 PM

the new one should make it easier imo - https://kian-wrangler-configuration.cloudflare-docs-github.pages.dev/workers/wrangler/configuration/#local-development-settings

K

kian•8/19/22, 10:37 PM

feedback is welcome

TTheSunSide ▲ [WARNING] This worker is bound to live services: MAIL_FETCH (mail@local), LOGG...

T

TilonOP•8/19/22, 11:05 PM

Yeah, the thing is that it says for me:
„Support for service bindings in local mode is experimental and may change.“

which sounded like it „could“ work with the latest Wrangler version. I was just curious if it is actually working for anybody.

TTilon Yeah, the thing is that it says for me: „Support for service bindings in local m...

T

TheSunSide•8/19/22, 11:15 PM

https://github.com/cloudflare/wrangler2/pull/1503 might help, not quite sure how to do it

GitHub

feat: zero config multiworker development (local mode) by threepoin...

Preamble: Typically, a Worker has been the unit of a javascript project on our platform. Any logic that you need, you fit into one worker, ~ 1MB of javascript and bindings. If you wanted to deploy ...

TTheSunSide https://github.com/cloudflare/wrangler2/pull/1503 might help, not quite sure how...

T

TilonOP•8/19/22, 11:31 PM

Thx, I am checking it out

J

James•8/21/22, 3:40 PM

Workers Sites does work well with Wrangler 2 fwiw, if you'd prefer to just do that

J

James•8/21/22, 3:41 PM

If you'd prefer not to migrate, the docs for Workers Sites + wrangler 2 are pretty sparse, but I've a working example with my project at https://github.com/Cherry/placeholders.dev.

J

James•8/21/22, 3:42 PM

Not officially while Functions are still technically "beta", but that's the goal long-term, yes.

J

James•8/21/22, 3:43 PM

The Pages way of running Workers: https://developers.cloudflare.com/pages/platform/functions/

JJacob Since migrating from cloudflare/wrangler to wrangler (v2.0.7 through v2.0.26) I ...

M

Max (@rozenmd)•8/22/22, 10:46 AM

do you mind filing an issue for this? https://github.com/cloudflare/wrangler2/issues/new/choose

M

Max (@rozenmd)•8/22/22, 10:48 AM

ah cheers, knew it sounded familiar

Tttraenkler after upgrading to wrangler 2 the github cloudflare/wrangler-action fails for al...

H

Hello, I’m Allie!•8/22/22, 2:42 PM

Is your repo open-source?

Tttraenkler unfortunately not

H

Hello, I’m Allie!•8/22/22, 2:44 PM

Is the project static, or dynamic?

Tttraenkler both, if i understand correctly. we store some assets in the kv store statically...

H

Hello, I’m Allie!•8/22/22, 2:46 PM

Just trying to figure out how easy it would be for you to transition to #pages-discussions, which is recommended above

workers-sites

workers-sites

workers-sites

workers-sites now. Is

workers-site

workers-site

workers-site

workers-site where the Worker lives, or where your assets live?

Tttraenkler both, if i understand correctly. we store some assets in the kv store statically...

H

Hello, I’m Allie!•8/22/22, 2:46 PM

Basically, with Pages, you would only pay for serving the on-demand assets, all static asset requests would be free.

B

Bobakanoosh•8/22/22, 10:34 PM

I'm deploying a Nuxt 3 SSR app through Github actions to workers, via wrangler 2.

However, I cannot for the life of me get environment variables for the nuxt app to work. No luck with google.

Here's my cloudflare step:

      - name: Publish to Cloudflare
        uses: cloudflare/wrangler-action@2.0.0
        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}
          accountId: ${{ secrets.CF_ACCOUNT_ID }}
          command: publish --env staging
          environment: staging
        env:
          NUXT_PUBLIC_API_AUTH_URL: ${{ secrets.NUXT_PUBLIC_API_AUTH_URL }}

      - name: Publish to Cloudflare
        uses: cloudflare/wrangler-action@2.0.0
        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}
          accountId: ${{ secrets.CF_ACCOUNT_ID }}
          command: publish --env staging
          environment: staging
        env:
          NUXT_PUBLIC_API_AUTH_URL: ${{ secrets.NUXT_PUBLIC_API_AUTH_URL }}

      - name: Publish to Cloudflare
        uses: cloudflare/wrangler-action@2.0.0
        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}
          accountId: ${{ secrets.CF_ACCOUNT_ID }}
          command: publish --env staging
          environment: staging
        env:
          NUXT_PUBLIC_API_AUTH_URL: ${{ secrets.NUXT_PUBLIC_API_AUTH_URL }}

      - name: Publish to Cloudflare
        uses: cloudflare/wrangler-action@2.0.0
        with:
          apiToken: ${{ secrets.CF_API_TOKEN }}
          accountId: ${{ secrets.CF_ACCOUNT_ID }}
          command: publish --env staging
          environment: staging
        env:
          NUXT_PUBLIC_API_AUTH_URL: ${{ secrets.NUXT_PUBLIC_API_AUTH_URL }}

If I locally have a

.env

.env

with the

NUXT_PUBLIC_API_AUTH_URL

NUXT_PUBLIC_API_AUTH_URL

NUXT_PUBLIC_API_AUTH_URL

NUXT_PUBLIC_API_AUTH_URL variable set, everything works fine. Do I have to somehow create a

.env

.env

with github actions before publishing to cloudflare..?

I only use [[services]] in the wrangler.toml

Similar Threads

Similar Threads

Similar Threads