| Age | Commit message (Collapse) | Author |
|
Build/upload logic for FreeBSD and OpenBSD packages now lives in
~/git/conf/packages/ as a Makefile + shell scripts. Magefile retains
only build, test, vet, and lint targets.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
|
Use pkg_sign -s signify2 after pkg_create to produce signed packages.
The signify private key lives at /etc/signify/custom-pkg.sec on the
OpenBSD build host (fishfinger).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
|
New mage targets:
- pkgFreebsd: cross-compile, package on f0, upload to repo
- pkgOpenbsd: cross-compile, package on fishfinger, upload to repo via f0
- pkg: both of the above
- buildFreebsd: cross-compile for FreeBSD amd64
Legacy openbsd/deployOpenbsd targets preserved for backward compat.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
|
When Prometheus alerts stop firing, they were previously left in state
and became stale. Now they are automatically removed when no longer
in the firing alerts list from Prometheus.
Also fix Magefile Openbsd target to run build before deploy sequentially
instead of using mg.Deps which runs them in parallel.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
|
|
|
This commit introduces two new optional parameters to the check configuration:
- `randomSpread`: This parameter allows specifying a random sleep time up to N seconds before a check is executed. This is useful to avoid all checks running at the same time.
- `RunInterval`: This parameter defines the minimum interval in seconds between two executions of a check. This is useful if gogios is run more frequently than a specific check should be.
The `README.md` has been updated to document these new features.
fix: Fix deadlock when skipping checks
This commit also fixes a deadlock that occurred when a check was skipped due to the `RunInterval` setting. The `inputWg.Done()` was not being called, causing the main goroutine to wait forever.
build: Replace Taskfile with Magefile
The `Taskfile.yml` has been replaced with a `Magefile.go` to manage the build process. This provides more flexibility and is more idiomatic for Go projects.
|