it is 248KB if I calculate gzip

Chaika•10/25/24, 3:26 PM

the gzipped size is what matters. If you do wrangler deploy it tells you the size. Did it still fail to deploy or something?

RaiyanOP•10/25/24, 3:26 PM

I haven't deployed it, I added a big ass library and it added around 500KB to the bundle

Chaika•10/25/24, 3:27 PM

you can just dump it to a folder like

wrangler deploy --outdir bundled/ --dry-run

wrangler deploy --outdir bundled/ --dry-run

, and should tell you the raw and gzipped

RaiyanOP•10/25/24, 3:31 PM

I used this command to get the exact size which was 1.2MB, then used esbuild as wrangler uses esbuild to bundle to get the meta file and from there, I saw the library adds around 500KB, but using gzip utility, I got 248KB to be the file size

RaiyanOP•10/25/24, 3:32 PM

there is now static hosting in workers, how that works?

RaiyanOP•10/25/24, 3:32 PM

is it bundled with the worker itself?

RRaiyan I used this command to get the exact size which was 1.2MB, then used esbuild as ...

Chaika•10/25/24, 3:32 PM

Not sure I would trust the gzip utility, could be different compression levels and such, I would go with the dry run or actual deployment

RRaiyan is it bundled with the worker itself?

Chaika•10/25/24, 3:32 PM

completely separate

CChaika Not sure I would trust the gzip utility, could be different compression levels a...

RaiyanOP•10/25/24, 3:33 PM

oh I just saw it also shows the gzip size in dry run, didn't notice that, it is 248KB

Chaika•10/25/24, 3:34 PM

then no need to worry about size after all

RaiyanOP•10/25/24, 3:34 PM

thanks for the help, I started wondering where can I deploy it then

DiamondDragon•10/25/24, 4:17 PM

Reading more into RPCs

https://github.com/cloudflare/workers-sdk/issues/1182

am I correct assuming if one has a worker calling out to another 2 workers using RPC, then in dev you have to have

wrangler dev

wrangler dev

running on all 3 workers or rely on the other 2 workers being in production in order to work locally with the original worker that calls out to the others?

GitHub

RFC: Multi-worker development · Issue #1182 · cloudflare/workers-sdk

We announced service bindings in November last year, and the APIs in production went GA last month. You can now "bind" workers and make calls between them. So, for example, let's say ...

Ffry69 You `_acme` CNAME (from your sass domain/platform) needs to point to Cloudflare ...

Constantin•10/25/24, 5:21 PM

that's right, but i was curious if i can change the cloudflare.com part in the dcv TXT _acme record, with my sass domain

Constantin•10/25/24, 5:21 PM

so when tenants add the _acme record, to appear more proffesionall showing my domain instead cloudflare

CConstantin that's right, but i was curious if i can change the cloudflare.com part in the d...

fry69•10/25/24, 5:21 PM

No. That is needed so that Cloudflare can request certificates on your behalf.

CConstantin so when tenants add the _acme record, to appear more proffesionall showing my do...

fry69•10/25/24, 5:22 PM

That is the goal.The CNAME is only needed for the above reason (ACME challenge) and will not show up for your clients.

fry69•10/25/24, 5:24 PM

Also this has little to do with workers

Constantin•10/25/24, 5:24 PM

hmm

Constantin•10/25/24, 5:25 PM

looks like the _acme should pe placed by each tenant in their dns

CConstantin looks like the _acme should pe placed by each tenant in their dns

fry69•10/25/24, 5:25 PM

Correct, you need that CNAME for each domain.

Constantin•10/25/24, 5:26 PM

right, so i was curious if i can buy sume cloudflare service to change the ...dcv.cloudflare.com with ...dcv.greatoutdoors-dns.live

Constantin•10/25/24, 5:27 PM

so i can provide to my tenants

CConstantin right, so i was curious if i can buy sume cloudflare service to change the ...dc...

fry69•10/25/24, 5:27 PM

No. This will not work for above reason. Cloudflare needs control over this CNAME so it can answer ACME challenges or Cloudflare cannot setup TLS certificates for the domains, which are needed for the proxy front end.

Constantin•10/25/24, 5:31 PM

well, for now i managed to make them work without placing the _acme TXT record. but i think the domain will not workanymore after the certificate will expire

Constantin•10/25/24, 5:32 PM

so is needed for CF to reissue (automatically) a new certificate.

CConstantin so is needed for CF to reissue (automatically) a new certificate.

fry69•10/25/24, 5:32 PM

Correct.

fry69•10/25/24, 5:32 PM

Every three months.

Constantin•10/25/24, 5:33 PM

can this process be tested somehow, without having to wait 3months?

Constantin•10/25/24, 5:34 PM

or i should just trust that'll work

Constantin•10/25/24, 5:34 PM

if the _txt record is there

CConstantin well, for now i managed to make them work without placing the _acme TXT record. ...

Chaika•10/25/24, 5:34 PM

You can just use http validation

Chaika•10/25/24, 5:34 PM

then no records needed at all other then the one normal cname for http

Constantin•10/25/24, 5:35 PM

this one, of adding records, looks more professional, imho

Chaika•10/25/24, 5:35 PM

doing more work looks more professional?

Chaika•10/25/24, 5:36 PM

not sure I understand that but txts are a bit less possible to break

CConstantin right, so i was curious if i can buy sume cloudflare service to change the ...dc...

Chaika•10/25/24, 5:36 PM

I don't see any reason why you couldn't simply chain cnames, ex, you'd make <hostname>.dcv.yoursite.com unproxied cname to actual dcv.cloudflare.com. It wouldn't be very scalable though, you'd need a record on your end for each customer

Constantin•10/25/24, 5:39 PM

i'll give http validation a try

Constantin•10/25/24, 5:41 PM

it seems to be less invasive, if the tenant already have an existing _acme record

Constantin•10/25/24, 5:42 PM

they don't have to replace with my own and break their dns

CConstantin they don't have to replace with my own and break their dns

Chaika•10/25/24, 5:43 PM

Typically you're only going to use non-ent cf for saas on subdomains

Chaika•10/25/24, 5:43 PM

and the _acme record would be on the subdomain as well

Chaika•10/25/24, 5:44 PM

so very little chance of conflicting with something, and if you do, it probably shouldn't be there

Constantin•10/25/24, 5:44 PM

indeed, you're correct

Constantin•10/25/24, 5:44 PM

such a great experience with workers and rpc calls between them!

Constantin•10/25/24, 5:45 PM

kudos all!

Constantin•10/25/24, 5:49 PM

@Chaika and with http validation, cloudflare will do the validation automatically, or i should run/call the cf apis to reissue the certs?

CConstantin @Chaika and with http validation, cloudflare will do the validation automaticall...

Chaika•10/25/24, 5:50 PM

automagically

Chaika•10/25/24, 5:51 PM

CF uses CF For SaaS/Custom Hostnames for Pages Custom Domains (external domains and on cf ones) and for R2 Custom domains, etc. It's pretty nice, just takes care of the hard stuff for you

Constantin•10/25/24, 5:53 PM

nais, nais

fry69•10/25/24, 5:58 PM

Also it is reasonably easy to automate updating certs and dependent DNS records with certbot and DNS APIs like Cloudflare -> https://github.com/fry69/certbot-cloudflare-dns-updaters

it is 248KB if I calculate gzip

Similar Threads