Pipeline: nieuwe Gitea-namen en deploy met SSH-sleutel (geen wachtwoord meer)
Continuous Integration / config (pull_request) Successful in 6s
Continuous Integration / prepare (pull_request) Successful in 29s
Continuous Integration / build-production (pull_request) Skipped
Continuous Integration / test (pull_request) Successful in 36s
Continuous Integration / build (pull_request) Successful in 44s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 2m16s
Continuous Integration / deploy-production (pull_request) Skipped
Continuous Integration / config (pull_request) Successful in 6s
Continuous Integration / prepare (pull_request) Successful in 29s
Continuous Integration / build-production (pull_request) Skipped
Continuous Integration / test (pull_request) Successful in 36s
Continuous Integration / build (pull_request) Successful in 44s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 2m16s
Continuous Integration / deploy-production (pull_request) Skipped
TEST_/PROD_-variabelen (DEPLOY_PATH, UMAMI, SENTRY) en TEST_HOST_*/PROD_HOST_* secrets. Wachtwoord-terugval (sshpass) verwijderd; StrictHostKeyChecking=accept-new. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -50,9 +50,9 @@ env:
|
||||
# (Repository → Settings → Actions → Variables), zodat het pad per omgeving
|
||||
# aangepast kan worden zonder de workflow zelf te wijzigen. Zie
|
||||
# deployment-instructions.md voor de eenmalige setup van deze variable.
|
||||
DEPLOY_PATH: ${{ vars.DEPLOY_PATH_TEST }}
|
||||
DEPLOY_PATH: ${{ vars.TEST_DEPLOY_PATH }}
|
||||
DEPLOY_ENVIRONMENT_PRODUCTION: production
|
||||
DEPLOY_PATH_PRODUCTION: ${{ vars.DEPLOY_PATH_PRODUCTION }}
|
||||
DEPLOY_PATH_PRODUCTION: ${{ vars.PROD_DEPLOY_PATH }}
|
||||
|
||||
jobs:
|
||||
# Geeft de env-variabelen hierboven door als job-outputs, zodat ze ook
|
||||
@@ -133,18 +133,17 @@ jobs:
|
||||
|
||||
- name: Build
|
||||
env:
|
||||
VITE_UMAMI_SCRIPT_URL: ${{ vars.VITE_UMAMI_SCRIPT_URL }}
|
||||
# Gitea-variable heet VITE_UMAMI_WEBSITE_ID_TEST (niet zonder suffix),
|
||||
# analoog aan VITE_UMAMI_WEBSITE_ID_PRODUCTION in de build-production
|
||||
# job hieronder. Linkerkant (VITE_UMAMI_WEBSITE_ID) is wél altijd
|
||||
VITE_UMAMI_SCRIPT_URL: ${{ vars.TEST_UMAMI_SCRIPT_URL }}
|
||||
# Gitea-variable heet TEST_UMAMI_WEBSITE_ID (PROD_UMAMI_WEBSITE_ID in de
|
||||
# build-production job hieronder). Linkerkant (VITE_UMAMI_WEBSITE_ID) is wél altijd
|
||||
# gelijk: dat is de Vite-buildtime-envvar-naam die de app verwacht
|
||||
# (zie src/components/UmamiAnalytics.tsx), niet aan te passen.
|
||||
VITE_UMAMI_WEBSITE_ID: ${{ vars.VITE_UMAMI_WEBSITE_ID_TEST }}
|
||||
VITE_UMAMI_WEBSITE_ID: ${{ vars.TEST_UMAMI_WEBSITE_ID }}
|
||||
# Sentry DSN is niet gevoelig (veilig om in de client-bundle te zitten),
|
||||
# daarom een Gitea Actions "vars"-waarde i.p.v. een secret. Optioneel:
|
||||
# als deze niet is ingesteld, wordt Sentry-logging simpelweg overgeslagen
|
||||
# (zie src/main.tsx) en blijft alleen console-logging actief.
|
||||
VITE_SENTRY_DSN: ${{ vars.VITE_SENTRY_DSN }}
|
||||
VITE_SENTRY_DSN: ${{ vars.TEST_SENTRY_DSN }}
|
||||
# Build-time tag die de Sentry environment (test vs. production) bepaalt;
|
||||
# zie src/main.tsx. De SentryTestButton zelf is hier los van: die is
|
||||
# uitsluitend zichtbaar bij `pnpm dev`, in geen enkele build (zie
|
||||
@@ -203,14 +202,14 @@ jobs:
|
||||
# "website"-entry (test.slpsoftware.nl vs slpsoftware.nl) heeft een
|
||||
# eigen ID, anders komt productieverkeer in de teststatistieken
|
||||
# terecht (of andersom). Vereist dus een eigen Umami-website +
|
||||
# Gitea-variable VITE_UMAMI_WEBSITE_ID_PRODUCTION — zie umami-setup.md.
|
||||
VITE_UMAMI_SCRIPT_URL: ${{ vars.VITE_UMAMI_SCRIPT_URL }}
|
||||
VITE_UMAMI_WEBSITE_ID: ${{ vars.VITE_UMAMI_WEBSITE_ID_PRODUCTION }}
|
||||
# VITE_SENTRY_DSN wordt wél gedeeld met de testbuild: één Sentry-
|
||||
# Gitea-variable PROD_UMAMI_WEBSITE_ID — zie umami-setup.md.
|
||||
VITE_UMAMI_SCRIPT_URL: ${{ vars.PROD_UMAMI_SCRIPT_URL }}
|
||||
VITE_UMAMI_WEBSITE_ID: ${{ vars.PROD_UMAMI_WEBSITE_ID }}
|
||||
# TEST_SENTRY_DSN en PROD_SENTRY_DSN hebben dezelfde waarde: één Sentry-
|
||||
# project voor beide omgevingen, VITE_APP_ENV hieronder tagt de
|
||||
# events al als 'test' vs 'production'. Splits dit pas op als je
|
||||
# ooit aparte Sentry-projecten per omgeving wilt.
|
||||
VITE_SENTRY_DSN: ${{ vars.VITE_SENTRY_DSN }}
|
||||
VITE_SENTRY_DSN: ${{ vars.PROD_SENTRY_DSN }}
|
||||
VITE_APP_ENV: ${{ env.DEPLOY_ENVIRONMENT_PRODUCTION }}
|
||||
run: pnpm run build
|
||||
|
||||
|
||||
Reference in New Issue
Block a user