nostrweb/.woodpecker.yml

pipeline:
  build:
    image: node:18-slim
    commands:
      - npm ci
      - npm run build
  prepare_release:
    when:
      event: tag
      branch: master
      tag: v*
    image: node:18-slim
    commands:
      - tools/ci-make-release-targz.sh
  create_release:
    when:
      event: tag
      branch: master
      tag: v*
    image: plugins/gitea-release
    settings:
      api_key:
        from_secret: releaser_auth_token
      base_url: https://git.qcode.ch
      files: nostrweb.tar.gz
      note: "automated release by ${CI_SYSTEM_HOST} \nbuild id: ${CI_BUILD_NUMBER}"
ci: set up a continuous build of the app the CI is a selfhosted woodpecker instance: - https://woodpecker-ci.org/ - https://laszlo.cloud/drone-community-edition-what-is-included 2 years ago			`pipeline:`
			`build:`
			`image: node:18-slim`
			`commands:`
			`- npm ci`
			`- npm run build`
ci: add steps to create releases on vA.B.C tag events the steps create a tar.gz with all files found in dist/ dir. additionally, an ad-hoc build.txt file is created with build info. the bot then creates a release and uploads the tar.gz as an artifact. the idea is that all nostr web app instances are notified about the new release, download the tar.gz and update their local copy. this is not yet implemented. 2 years ago			`prepare_release:`
			`when:`
			`event: tag`
			`branch: master`
			`tag: v*`
			`image: node:18-slim`
			`commands:`
			`- tools/ci-make-release-targz.sh`
			`create_release:`
			`when:`
			`event: tag`
			`branch: master`
			`tag: v*`
			`image: plugins/gitea-release`
			`settings:`
			`api_key:`
			`from_secret: releaser_auth_token`
			`base_url: https://git.qcode.ch`
			`files: nostrweb.tar.gz`
			`note: "automated release by ${CI_SYSTEM_HOST} \nbuild id: ${CI_BUILD_NUMBER}"`