dennisthiessen
8856e7c273
My Gatsby Deployment pipeline / build-and-deploy (push) Successful in 4m4s
Replace the HTML5-UP "Strata" theme with a Swiss-minimal single-page design (plain CSS, Space Grotesk / Hanken Grotesk / Space Mono). Rewrite copy for current positioning: Staff Data, Analytics & AI Engineer at Swisscom, open to new work. Experience shown as a pipeline timeline; contact simplified to email + LinkedIn (drop the broken form). Prune unused deps (lightbox, FontAwesome, sass/gatsby-plugin-sass) and the old SCSS, fonts and gallery assets. Fix package.json metadata. Harden the Gitea deploy: merge build+deploy into one job (removes the deprecated artifact upload/download handoff), bump Node 18 -> 20, use npx gatsby build. Rename .nvrmc -> .nvmrc and refresh the README. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
777 B
777 B
thiessen.io
Personal site of Dennis Thiessen — Staff Data, Analytics & AI Engineer (Bern, Switzerland).
Built with Gatsby 5 and React 18. Single-page, Swiss-minimal design; styles are plain CSS in src/assets/style.css (no preprocessor).
Develop
npm install --legacy-peer-deps
npx gatsby develop # http://localhost:8000
Build
npx gatsby build # output in ./public
Use Node 20 (see .nvmrc).
Deploy
Pushing to master triggers the Gitea Actions workflow in
.gitea/workflows/workflow.yaml, which builds the site and rsyncs public/
to the web server over SSH. It relies on these repository secrets:
SSH_PRIVATE_KEY, SSH_KNOWN_HOSTS, DEPLOY_USER, DEPLOY_HOST, DEPLOY_PATH.