cvsickle/profile
cvsickle/profile
Watch
1
0
Fork
You've already forked profile
 0
mirror of https://github.com/cvsickle/profile.git synced 2026-10-03 01:31:09 -04:00
Code Issues Projects Releases Packages 1 Wiki Activity
Simple container for displaying some information about me. https://www.cvsickle.com
50 commits 1 branch 15 tags 596 KiB
  • CSS 42.1%
  • HTML 30.3%
  • JavaScript 16.3%
  • Dockerfile 7.4%
  • Shell 3.9%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
cvsickle 00dc4a9cbc fix for mobile view
2026-08-28 21:27:12 -04:00
.woodpecker another fix to codeberg sync 2026-08-28 21:03:14 -04:00
site fix for mobile view 2026-08-28 21:27:12 -04:00
docker-compose.yaml commit from dev container 2026-08-01 14:20:47 +00:00
docker-entrypoint.sh first commit 2026-07-31 20:37:07 -04:00
Dockerfile commit from dev container 2026-08-01 14:20:47 +00:00
nginx.conf commit from dev container 2026-08-01 14:20:47 +00:00
readme.md added readme with pipeline explanation 2026-08-01 18:52:12 -04:00

readme.md

Profile

This is just a simple container for displaying some information about me on the root of my domain, but it also serves as an example of my pipeline powered by Woodpecker CI and Flux CD.

Repository Mirrors

Pipeline

When a release is created, the GitHub repository triggers the forgejo_build.yaml automation to run on the Woodpecker instance running on my k3s Kubernetes Cluster.

Woodpecker then builds the image, tags it with the GitHub release tag, and pushes the image to my Forgejo instance.

On my cluster, Flux tracks this package repo for updates. When one is found, it updates the corresponding deployment manifest.

In a production environment, this automation would ideally create a pull request. This being a homelab cluster, I've opted to allow this update to be automatically pushed.