Request: publish prebuilt server

[phyzical]

similar to how the action's dist is commited,

any chance the same can happen for server? (or at the very least the output for npm run build:aws-lambda)

that way Terraform wise we can use renovate to pin version and when a new github release happens we can just download and repackage the lambda's source?

or maybe simply as seperate zips in the releases for each type?

[qoomon]

Could you give me an example of cose how you'd like to uses those packages? And what about the configuration how you'd like to pass them? As environment variables one big environment jso. Variable or as a file. I need some sparring to fin a proper solution.

[phyzical]

AFAIK the lambda src doesn't need any envs on build? those are provided to the implementation/usage lambda side.

im after the output of npm run build:aws-lambda, if that makes sense?

something like the following in your server-build

build-lambda:
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main'
    defaults:
      run:
        working-directory: &working-directory server
    steps:
      - uses: actions/checkout@v6
        with:
          sparse-checkout: *working-directory
          sparse-checkout-cone-mode: false

      # build the action
      - uses: jdx/mise-action@v3
        with:
          working_directory: *working-directory

      - run: npm ci
      - run: npm run test
      - run: npm run build:aws-lambda
      - name: Upload Lambda Build Artifact
        uses: actions/upload-artifact@v3
        with:
          name: lambda-build
          path: server/dist

granted this doesnt commit per tag/release but itll atleast get 1 step closer to a download and go approach

[qoomon]

What about an npm package?

[phyzical]

its basically the same level of work terraform side, ideally you wouldn't use node at all.

all we would need is a way to download the dist output to zip it up and send it to the lambda.

[qoomon]

Okay got it. However the dist would include a config already that's why I had ask how you'd like to configure the server

[phyzical]

hmm, okay tbh i must be using all defaults then?

i just cloned the repo,npm install, built, send to the lambda and it worked

[qoomon]

@phyzical actually you are right :-D all relevant configuration parameters are set by environment variables anyway.

[qoomon]

I'll work on this in the beginning of march after m vacation

[qoomon]

I'll guess I need to split up this repo in action and server repo to have separate releases.

[phyzical]

no rush 👍

yeah best bet would just perform a seperate run for each typ. when you use upload-artifact youll just name it accordingly.

you could keep them all in the same run and delete the dist between each upload though too