Climate change nightmare, tech edition: #CI workflow using #Nix on #Gentoo to fine-tune a #JVM implementation of a #blockchain-enabled #LLM.

Thanks for inspiration, @faassen!

Keep your commits consistent!
forgejo-commit-path-rules v0.2.3 ensures your commit messages align with your file changes.

Enforce commit message and file path rules in your repo!

Written in Rust
Repo: https://codeberg.org/kemitix/forgejo-commit-path-rules
A ForgeJo Action/CLI Tool

What's New:

- Coloured highlights in logging (supports --no-colour)
- all matching strategy for paths (default is any)
- Built in templates: docs, feature, tests and fixes

Usage:

- Define rules in .forgejo/commit-path-rules.toml
- Run via CLI or ForgeJo Action

Install:
cargo install forgejo-commit-path-rules

CLI Usage:
forgejo-commit-path-rules --workspace . --no-colour

Forgejo Action:

 jobs:
  validate:
   steps:
    - uses: actions/checkout@v3
      with:
        fetch-depth: 0
    - name: Run forgejo-commit-path-rules
      uses: kemitix/commit-path-rules@v0.2.3
      with:
        args: --verbose

the other #rustlang thingy that's been cooking (and just passed a #ci run) is called #taggart.

it uses #tengri to pop up an interactive table to edit things, namely: the #id3 tags of music releases

its purpose? why, to make it easier to prepare a certain pile of content (that we've accumulated with a friend over the past, what, 6-7 years), for publication in a sovereign #faircamp instance! but none of it's well-tagged and existing interactive mediatag editors are ugh

https://codeberg.org/unspeaker/taggart

WordPress kann schnell installiert und verwendet werden. Aber man kann es auch übertreiben und via Git bereitstellen, um einige Vorteile zu haben. In diesem Artikel findest du Informationen darüber, warum das eine gute Idee sein kann und welche Unwägbarkeiten auf dich warten.

https://epiph.yt/blog/2025/wordpress-deployment-via-git/

forgejo-todo-checker v1.3.2: Checks your source files for TODO and FIXME comments, where they don't have an open issue number

Written in Rust
Repo: https://codeberg.org/kemitix/forgejo-todo-checker
A ForgeJo Action.

What's new

- bug fix - hadn't updated the version of rust used in the docker image

Install

cargo install forgejo-todo-checker

CLI Usage

forgejo-todo-checker --workspace $PWD \
    --site https://git.kemitix.net \
    --repo kemitix/forgejo-todo-checker

This should allow you to check locally that your TODO and FIXME comments are valid before you push the change to your CI.

CI

forgejo-todo-checker is primarily a Forgejo Action:

jobs:
  tests:
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Check TODOs
        uses: kemitix/todo-checker@v1.3.2

If you have any TODO or FIXME comments in your code that doesn't have an associated and open issue, then this will fail the build.

So I want to set up a #CI pipeline on my webserver to serve static sites.

I already have a @caddy setup that can serve static files, as well as a bunch of other stuff that all runs in #Docker containers. But I would like to have a CI pipeline that will pick up my repository changes, and build and deploy stuff to a directory that #Caddy can serve.

Now, how ridiculous would it be to have:

- an SSH server running in a Docker container
- @WoodpeckerCI, also in Docker

and get Woodpecker to build the site and use scp to copy files over to the SSH server, that will have a shared volume with the Caddy container that maps to the /var/www directory?

I am not ready to set up a whole @forgejo instance to serve from Forgejo Pages. Plus, why use the Pages thing when I have a perfectly good Caddy server running already, that would be serving the Forgejo instance anyway?

Why not some sort of S3 compatible service in a container?
Why not FTP?
How many containers can a guy run?
Am I losing my mind (probably)?

The typical #FOSS #dev lifecycle:

1. #showerthought idea
2. git init, start #CI pipeline
3. code, don't forget #TDD

It is great for doing what you love to do as a coder: #coding. It is less great if over time your coded work becomes popular, and all kinds of boring other considerations must be dealt with.

One easily ends up in a #OneManArmy situation, and if not delegating timely, on a burnout vector.

This kind of ad-hoc #ShowDontTell also leads to #TechnosphereMyopia: tech-only perspective.

forgejo-todo-checker v1.3.0: Checks your source files for TODO and FIXME comments, where they don't have an open issue number
Written in Rust
Repo: https://git.kemitix.net/kemitix/forgejo-todo-checker
A ForgeJo Action.

What's new:

- add cli args to help run locally

Install:

cargo install forgejo-todo-checker

CLI Usage:

forgejo-todo-checker --workspace $PWD \
    --site https://git.kemitix.net \
    --repo kemitix/forgejo-todo-checker

This should allow you to check locally that your TODO and FIXME's comments are valid before you push the change to you CI.

CI:

forgejo-todo-checker remains primarily a Forgejo Action:

jobs:
  tests:
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Check TODOs
        uses: kemitix/todo-checker@v1.3.0

If you have any TODO or FIXME comments in your code that doesn't have an associated and OPEN issue, then this will fail the build.

No more builds breaking without notice.

I wanted to play with home automation for a while now so yesterday I bought a few lights in Ikea, fired up a Home Assistant and made a webhook that I added to my GitLab, so...

New Blog Post: "Wrapping Elephants in Snowflakes"

If you're working with Gradle and Nix, this post is for you! Learn how to bridge the gap between Gradle's dynamic dependency management and Nix's sandboxed builds—without the hassle.

Read the full post and discover the 2025 solution! https://britter.dev/blogs/2025-01-02-gradle-nix/

shout out to @Codeberg for launching #CodebergActions #CI

after some fiddling with that base image to use, i decided to go with #nixos/#nix

and so, my #diy #tui #daw now has a green check https://codeberg.org/unspeaker/tek/actions/runs/690/jobs/0

now, to figure out nix and #cargo caching...

I love how fast the curl CI jobs have become. In less than 5 minutes, we see success or failures in more than 100 build combinations. Huge.

Many thanks to @vsz for the heavy lifting!
#curl #ci

AI email clients are officially outdated and being replaced by CI email clients. CI stands for "Cat Insertion."

Are you trying to read an email? A picture of a cat is overlaid on top, blocking half the message. Are you trying to write an email? Our CI autocomplete helpfully inserts cat pictures that have nothing to do with what you were trying to write.

You can opt out of CI features in settings if you're a Luddite who hates progress, but our app will forget your settings every time you relaunch it.

Also, all release notes are now written by cats.

Currently, our advanced CI features are only available on our email client. However, if you give us $1,000,000,000 in venture capital money, we hope to expand to put CI into a web browser, a word processor, a video chat meeting client, an operating system, and even hardware!

The future is meow.

#Caturday #CI #AI

Some surprising code execution sources in #bash

https://yossarian.net/til/post/some-surprising-code-execution-sources-in-bash

#ci #cicd #devoops #sre @sre @devops #devops