I would certainly start with Pages.. if you end up in a situation where you really can't do something, it isn't all that hard to switch to using worker sites for example later.

Howdy! glad I have found this chat, as it answered some of my questions already (about lack of logging, for example) Is there any way to deploy to pages and workers in the following way: 1. I have a

/.dist.sh

2. Running

./dist.sh

produces the following structure: -

./site

-

./site/functions/....js

-

./site/...html

And I would like to deploy

./site

to Pages. I tried to change the root - but then the

./dist.sh

is not accessible, may be I should put

dist.sh

into

./site

and just not clean that folder before generation But it seems wonky

how are you trying to run

./dist.sh

?

I put

./dist.sh

into the "Build command" of a Pages project

(reason I'm doing this is because I'm deploy a Scala.JS function, so I need to build it first)

does your project use npm?

nope, ./dist.sh just - bootstraps the tool I need to build the project - invokes it

I could possibly do a dummy NPM project that just delegates to my build tool Is having NPM going to help somehow?

most likely, I'm not sure how exactly it works 🤔 but I'm doing the same thing on my project using npm and it works good

I'm generating files on the fly, only difference is I'm using a single .mjs file instead of .sh, so mileage may vary

in my package.json, I have

npm run build

as

node build.mjs

which just runs my js file

you might be able to do the same with a

.sh

workers/pages filesystem is wonky

and so you manage to 1. generate your functions in a folder that isn't checked in 2. successfully deploy pages app with functions in that folder?

yup

I have a folder that's not even real, it's a submodule

and I generate files and insert them into said folder

in terms of functions, I'm pretty sure it'd be more or less the same deal

could be wrong

it all happens at build time, before the function(s) are deployed

Huh. I should spend more time on it then. For now I just 1. Build the functions on

main

2. Check them in into an orphan branch

cloudflare

under

/functions

subfolder 3. and I have Cloudflare Pages setup to work off of

cloudflare

branch, not

main

Which works for my purposes, but I miss all the preview environment and PR goodness

Good to hear that it works for someone else, perhaps I will succeed as well 🙂

oh don't* bother with the branch or submodules

if you can get your build script to run as an

npm run something

, 99% chance it'll build on pages/workers

pages is mostly built for frameworks, so the "build command" part probably isn't meant to handle shell-type commands

but if you can pack it into a

npm

command, you're most likely a-ok

1s

here's part of my package.json:

js
    "scripts": {
        "build": "node src/gendoc.mjs"
    },

by running

npm run build

I'm just executing a script. You could probably do the exact same thing with a

.sh

file

"build": "./dist.sh"

maybe?

I'll give it a go - previously Pages wouldn't pick up

functions

folder that was generated by the script May be I messed it up somehow. That's really the only part that didn't work - dynamically generated functions as part of ./dist.sh The rest worked a-ok I'll see if running it as part of the NPM build makes a difference, thank you 🙏 The problem is most likely in the chair, not the computer..