Tonight I'll be trying to set up a runner for Gitea actions. I hope to get it to "build" docker images automatically on changes, then publish them to Gitea's container image registry: https://docs.gitea.com/usage/packages/container
It'll be the first time I've worked with gitea actions and gitea runners, so lots of trial and error to be had!
*sigh* The fucking AI bots apparently found yet another expensive #gitea endpoint that doesn't seem to be blocked by the `REQUIRE_SIGNIN_VIEW = expensive` setting.
CPU has been constantly at 90+% again for almost two days now.
I hate how these dipshits have made running your own digital infrastructure a constant uphill battle.
If I ever meet one of these fucking clowns, they can prepare for a juicy knuckle sandwich. I crave violence.
#Microsoft 🖕 killed my #github account without warning, explanation or justification
Thank dog for #gitea!
github-monitor is now forgewatch!
I rebranded my PR monitoring daemon. The old name locked it to a single platform, but the vision has always been broader than that. "forgewatch" better reflects what the app is really about: watching over your code forge, wherever it lives.
Why the rename? Two reasons:
1. It's more general. The architecture doesn't depend on GitHub specifically, and I want to grow it to support GitLab, Gitea, and other forges over time.
2. It's more descriptive. "forgewatch" tells you exactly what it does -- it watches your forge for pull requests and keeps you notified via D-Bus and desktop notifications on Linux.
The daemon is async Python, runs as a systemd user service, and comes with an optional system tray indicator. Give it a look if you're a Linux dev who juggles PRs across repos.
https://github.com/dvoraj75/forgewatch
https://pypi.org/project/forgewatch/
#forgewatch #opensource #python #linux #devtools #foss #github #gitlab #gitea #asyncio #dbus #systemd
Async daemon with system tray indicator and CLI tools for monitoring GitHub pull requests with desktop notifications and systemd integration (Linux) - dvoraj75/forgewatch
Today I got my CI/CD pipeline running for Keyboard Vagabond
I'm quite happy with today's work in keyboardvagabond of running #gitea and getting CI/CD runners to run my custom build of piefed and push to my internal harbor registry, then deploy the migration job and restart the services.
Sometimes I'd do the build (locally), but forget to delete and recreate the db-migration job, which is now automatic - and it's faster.
Once I move the other builds, I can completely isolate more svcs from the internet #programming #selfhosted
@lw Pre-Forgejo, the #HardenedBSD project tried for a while to use #Gitea. But that fell over sideways with src and ports, especially with scraper bots continuously looking up each and every commit.
At the time, the problem stemmed from the fact that the #golang git package that everyone uses will load the entire repo history just to look up a single commit.
Rinse and repeat for thousands of hits per second, and kaboom!
HardenedBSD currently uses a self-hosted #GitLab Enterprise instance. We're hoping to eventually migrate to #Radicle.
🍱 Sean ☕
Patch Notification Robot 🔔
phryk 🏴
Micheal Shallop 🐧
JohnnyD
ragingHungryPanda
Mike Roach
sysadmin
bojkotiMalbona
Shawn Webb