<https://docs.github.com/en/actions/learn-github-actions/expressions#example>

M

Mitya•1/25/24, 11:02 AM

Thanks. So the full file would be as follows? Could you possibly elaborate on what precisely that

with/environment

with/environment

with/environment

with/environment part does? I know it's setting env vars, but what is the result of those operators i.e. the statement's intention?

name: Deploy

on:
  push:
    branches:
      - main

with:
  environment: ${{ github.ref_name == 'main' && 'worker-env-for-main' || 'worker-env-for-not-main' }}

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}

name: Deploy

on:
  push:
    branches:
      - main

with:
  environment: ${{ github.ref_name == 'main' && 'worker-env-for-main' || 'worker-env-for-not-main' }}

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}

name: Deploy

on:
  push:
    branches:
      - main

with:
  environment: ${{ github.ref_name == 'main' && 'worker-env-for-main' || 'worker-env-for-not-main' }}

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}

name: Deploy

on:
  push:
    branches:
      - main

with:
  environment: ${{ github.ref_name == 'main' && 'worker-env-for-main' || 'worker-env-for-not-main' }}

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}

M

Mitya•1/25/24, 11:02 AM

Appreciate the help. (Also, why do I need to get involved in specifying Linux versions? Is that just for GH not CF?)

K

kianOP•1/25/24, 11:09 AM

yep

K

kianOP•1/25/24, 11:09 AM

you need to tell GitHub what to run the Actions on

K

kianOP•1/25/24, 11:09 AM

same as if you wanted a Docker container, you still need to tell it that you want

ubuntu

ubuntu

ubuntu

ubuntu or

debian

debian

debian

debian or

alpine

alpine

alpine

alpine, etc

MMitya Thanks. So the full file would be as follows? Could you possibly elaborate on wh...

K

kianOP•1/25/24, 11:10 AM

environment

environment

environment

environment needs to be under the same

with

with

with

with as

apiToken

apiToken

apiToken

apiToken

K

kianOP•1/25/24, 11:10 AM

with

with

with

with are inputs that the action (in this case

wrangler-action

wrangler-action

wrangler-action

wrangler-action) accepts

K

kianOP•1/25/24, 11:11 AM

https://github.com/cloudflare/wrangler-action/blob/08514fdeceb93b6f0e9325780b4438218fcbe1c0/action.yml#L21-L22

M

Mitya•1/25/24, 11:15 AM

Aha, thanks. So:

name: Deploy

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'worker-env-for-main' || 'worker-env-for-not-main' }}
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}

name: Deploy

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'worker-env-for-main' || 'worker-env-for-not-main' }}
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}

name: Deploy

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'worker-env-for-main' || 'worker-env-for-not-main' }}
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}

name: Deploy

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: Deploy
    steps:
      - uses: actions/checkout@v3
      - name: Deploy
        uses: cloudflare/wrangler-action@v3
        with:
          environment: ${{ github.ref_name == 'main' && 'worker-env-for-main' || 'worker-env-for-not-main' }}
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}

M

Mitya•1/25/24, 11:15 AM

And presumably

secrets.CLOUDFLARE_API_TOKEN

secrets.CLOUDFLARE_API_TOKEN

secrets.CLOUDFLARE_API_TOKEN

secrets.CLOUDFLARE_API_TOKEN refers to a GH secret, not a Worker secret

K

kianOP•1/25/24, 11:15 AM

Yep

K

kianOP•1/25/24, 11:15 AM

If you want to publish your Worker with secrets from GitHub, you use

secrets

secrets

in

with

with

with

with

K

kianOP•1/25/24, 11:16 AM

jobs:
  deploy:
    steps:
      uses: cloudflare/wrangler-action@v3
      with:
        apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
        secrets: |
          SECRET1
          SECRET2
      env:
        SECRET1: ${{ secrets.SECRET1 }}
        SECRET2: ${{ secrets.SECRET2 }}

jobs:
  deploy:
    steps:
      uses: cloudflare/wrangler-action@v3
      with:
        apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
        secrets: |
          SECRET1
          SECRET2
      env:
        SECRET1: ${{ secrets.SECRET1 }}
        SECRET2: ${{ secrets.SECRET2 }}

jobs:
  deploy:
    steps:
      uses: cloudflare/wrangler-action@v3
      with:
        apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
        secrets: |
          SECRET1
          SECRET2
      env:
        SECRET1: ${{ secrets.SECRET1 }}
        SECRET2: ${{ secrets.SECRET2 }}

jobs:
  deploy:
    steps:
      uses: cloudflare/wrangler-action@v3
      with:
        apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
        secrets: |
          SECRET1
          SECRET2
      env:
        SECRET1: ${{ secrets.SECRET1 }}
        SECRET2: ${{ secrets.SECRET2 }}

K

kianOP•1/25/24, 11:16 AM

but otherwise,

${{ secrets.CLOUDFLARE_API_TOKEN }}

${{ secrets.CLOUDFLARE_API_TOKEN }}

${{ secrets.CLOUDFLARE_API_TOKEN }}

${{ secrets.CLOUDFLARE_API_TOKEN }} is just to say "use the API token from my GitHub secret called

CLOUDFLARE_API_TOKEN

CLOUDFLARE_API_TOKEN

CLOUDFLARE_API_TOKEN

CLOUDFLARE_API_TOKEN"

M

Mitya•1/25/24, 11:17 AM

Ah that's interesting - so you're saying specifying secrets in this way is an alternative to creating secrets via Wrangler i.e.

secret put

secret put

secret put

secret put?

K

kianOP•1/25/24, 11:20 AM

Yep

M

Mitya•1/25/24, 11:21 AM

Legendary. Thanks for your help.

M

Mitya•1/25/24, 11:24 AM

On a different topic, if I don't specify the

--env

--env

--env

--env arg when doing

wrangler secret put

wrangler secret put

wrangler secret put

wrangler secret put, is the secret available to all envs (in my TOML), or default to just one env in particular?

K

kianOP•1/25/24, 11:30 AM

defaults to the Worker name that’s in the top level

K

kianOP•1/25/24, 11:31 AM

envs are separate Workers, it’s purely a Wrangler abstraction

M

Mitya•1/25/24, 11:37 AM

But if I create a secret with the

--env

--env

--env

--env arg, that secret will be available only to the env specified, right? So

wrangler secret put foo --env "stage"

wrangler secret put foo --env "stage"

wrangler secret put foo --env "stage"

wrangler secret put foo --env "stage" would make it available only to my

stage

stage

stage

stage env, as created in my TOML?

I

ItsWendell•1/25/24, 3:12 PM

Hi all! I'm trying to create a shared package in my mono repo that holds the fonts used across projects. I want to be able in a worker to import these fonts, I was looking at https://developers.cloudflare.com/workers/wrangler/configuration/#bundling but I was curious what would be a good setup for this?

For example, the package name is

@acme/fonts

@acme/fonts

@acme/fonts

@acme/fonts which has the fonts in the package "files" definitions, which I want to be able to import as a

Data

Data

Data

Data / ArrayBuffer type in my worker (we need this for dynamic image generation). Should I use fetch in this case or what would be a good flow for this? I also wanna use

@acme/fonts

@acme/fonts

@acme/fonts

@acme/fonts in our Next.js deployment for example.

Configuration - Wrangler · Cloudflare Workers docs

Use a

wrangler.toml

wrangler.toml

configuration file to customize the development and deployment setup for your Worker project and other Developer Platform …

C

chand1012•1/25/24, 3:50 PM

Quick question, is there an easy way to load HTML into a file at build time of a worker? For example, the official documentation recommends a string that contains the HTML, like in the JAMStack app example: https://developers.cloudflare.com/workers/tutorials/build-a-jamstack-app/

Is there a way to have this be a separate template and load it in at build or runtime? It would be a lot easier to work with IMO if it was a separate file.

Build a todo list JAMstack application · Cloudflare Workers docs

All of the tutorials assume you have already completed the Get started guide, which gets you set up with a Cloudflare Workers account, C3 , and …

K

kianOP•1/25/24, 3:51 PM

Just import it

K

kianOP•1/25/24, 3:51 PM

import html from “./index.html”

Kkian import html from “./index.html”

C

chand1012•1/25/24, 3:56 PM

I wasn't aware that you could import HTML files in JS/TS, thanks!

A

Advany•1/25/24, 9:13 PM

Is there a library that allows me to do a eval action using a very limited subset of javascript? Something that fast. I was looking at edge runtime by vercel but that looking really heavy...

AAdvany Is there a library that allows me to do a eval action using a very limited subse...

I

Isaac McFadyen•1/25/24, 9:44 PM

You could try Boa?

I

Isaac McFadyen•1/25/24, 9:44 PM

https://github.com/boa-dev/boa

L

liam | helius.dev•1/26/24, 1:57 AM

What contributes to the requests per second on the workers metrics tab? It doesn't seem to directly map to external worker invocations

U

Unsmart•1/26/24, 4:15 AM

When you request the worker it will add to the request metrics

IIsaac McFadyen <https://github.com/boa-dev/boa>

A

Advany•1/26/24, 10:25 AM

thanks

K

Kirk Ouimet•1/26/24, 6:49 PM

Are encrypted environment variables stored in a hardware security module on Cloudflare?

K

kianOP•1/26/24, 7:13 PM

It’s out of date, everyone has access to them

P

piffie•1/26/24, 8:33 PM

The docs for the Workers Analytics Engine recommend for Grafana to use the altinity plugin, but since nov, grafana has an own version to host a worker in your environment that manages all connections - whats now the recommended path?

C

Cyb3r-Jak3•1/26/24, 8:50 PM

What’s the new way Grafana has?

D

don't die 🙅 don't die 🙅•1/26/24, 9:05 PM

sorry about the wrong channel but i cant find the general, where can i find help for cloudfare domains?

D

don't die 🙅 don't die 🙅•1/26/24, 9:05 PM

thank you

S

spaone•1/26/24, 9:57 PM

I have a pages site, how do I create a new worker?

J

Justintime•1/26/24, 11:38 PM

Anyone know if it's possible to cache a response for less than 1 second using the runtime API?

RRanjan Mangla I have links to files on my ftp server, I can't ssh into server

M

Murmeltier•1/26/24, 11:53 PM

saw you asked about FTP on Cloudflare Workers some days ago, maybe this is still relevant for you: https://www.npmjs.com/package/workerd-ftp

npm

workerd-ftp

[![npm version][npm-version-src]][npm-version-href]
[![npm downloads][npm-downloads-src]][npm-downloads-href]
[![bundle][bundle-src]][bundle-href]
[![Codecov][codecov-src]][codecov-href]. Latest version: 0.1.0, last published: 16 minutes ago. Start using workerd-ftp in your project by running

npm i workerd-ftp

npm i workerd-ftp

npm i workerd-ftp

npm i workerd-ftp. There are no other projects i...

Aamcclosky quick question: https://developers.cloudflare.com/workers/platform/betas/ indica...

M

Murmeltier•1/26/24, 11:58 PM

deploying a Worker using TCP Socket API "just worked" for us - my guess is the betas page is outdated.

JJustintime Anyone know if it's possible to cache a response for less than 1 second using th...

D

dave•1/27/24, 3:28 AM

What’s the use-case here?

I think you should be able to use cacheTtl on the fetch in a Worker to set it to 1 second.

CCyb3r-Jak3 What’s the new way Grafana has?

P

piffie•1/27/24, 7:23 AM

they recommend this now https://github.com/lablabs/cloudflare-exporter

GitHub

GitHub - lablabs/cloudflare-exporter: Prometheus CloudFlare Exporter

Prometheus CloudFlare Exporter. Contribute to lablabs/cloudflare-exporter development by creating an account on GitHub.

U

Unsmart•1/27/24, 3:32 PM

That doesn’t look like it supports workers analytics engine data

J

joel•1/27/24, 6:48 PM

Is there any way to install private npm packages via worker? I already tried putting the direct https into the package.json & using a .npmrc file but both didn’t work

U

Unsmart•1/27/24, 6:51 PM

Workers doesnt do any builds or anything you would install the private npm packages in your CI be it your local machine, github actions, or something similar

<https://docs.github.com/en/actions/learn-github-actions/expressions#example>

Similar Threads

Similar Threads

Similar Threads