June june · they/sie
0 followers · 0 following
  • Germany & Cyberspace

  • Does infrastructure crimes with Nix and Ansible.

  • Joined on 2024-01-14
Repositories
2
 Projects Packages Code Public activity Starred repositories
8
june commented on pull request CCCHH/ansible-infra#121 2026-07-11 23:11:49 +02:00
Update actions/upload-artifact action to v7

Fails.

june commented on pull request CCCHH/ansible-infra#120 2026-07-11 23:11:35 +02:00
Update actions/upload-artifact action to v6

Fails.

june closed pull request CCCHH/ansible-infra#120 2026-07-11 23:11:35 +02:00
Update actions/upload-artifact action to v6
june closed pull request CCCHH/ansible-infra#119 2026-07-11 23:11:21 +02:00
Update actions/upload-artifact action to v5
june commented on pull request CCCHH/ansible-infra#119 2026-07-11 23:11:19 +02:00
Update actions/upload-artifact action to v5

Fails.

june commented on pull request CCCHH/ansible-infra#118 2026-07-11 23:11:05 +02:00
Update actions/upload-artifact action to v4

Fails.

june closed pull request CCCHH/ansible-infra#118 2026-07-11 23:11:05 +02:00
Update actions/upload-artifact action to v4
june deleted branch separate_major_releases from CCCHH/ansible-infra 2026-07-11 22:55:51 +02:00
june pushed to main at CCCHH/ansible-infra 2026-07-11 22:55:51 +02:00
2a576495da
 separate multiple major release upgrades
june merged pull request CCCHH/ansible-infra#117 2026-07-11 22:55:50 +02:00
separate multiple major release upgrades
june approved CCCHH/ansible-infra#117 2026-07-11 22:55:43 +02:00
separate multiple major release upgrades

Nice improvement! I think this won't cause too much additional effort really and makes stuff just safer.

june suggested changes for CCCHH/ansible-infra#112 2026-07-11 13:47:02 +02:00
alloy(role): pull in alloy role that works from fux

Very nice moving away from the upstream role to a much simpler custom role!

june commented on pull request CCCHH/ansible-infra#112 2026-07-11 13:47:02 +02:00
alloy(role): pull in alloy role that works from fux

This can be moved into the next step or is there a reason to have this in a separate step?

june commented on pull request CCCHH/ansible-infra#112 2026-07-11 13:47:02 +02:00
alloy(role): pull in alloy role that works from fux

Do we want/need unpoller support? If not, I would rather keep this role simpler and remove it.

june commented on pull request CCCHH/ansible-infra#112 2026-07-11 13:47:02 +02:00
alloy(role): pull in alloy role that works from fux

Let's leave the tags at the playbook level.

june commented on pull request CCCHH/ansible-infra#112 2026-07-11 13:47:02 +02:00
alloy(role): pull in alloy role that works from fux

We only have the Debian case, so having this be distro-specific isn't needed. I would rather have this role just fail, if someone tries to run it on an unsupported platform, instead of just no…

june pushed to didays-de at CCCHH/ansible-infra 2026-07-09 22:20:14 +02:00
25bab80c58
 status(host): add monitoring for didays.de and staging
56392b776a
 public-reverse-proxy(host): add config for didays.de and staging
50cca22cfe Update docker.io/binwiederhier/ntfy Docker tag to v2.26.0
1ae4a39f57 Update all stable non-major dependencies
Compare 4 commits »
june created pull request CCCHH/ansible-infra#113 2026-07-09 22:19:18 +02:00
setup for didays.de website and staging
june pushed to didays-de at CCCHH/ansible-infra 2026-07-09 22:18:33 +02:00
7022ab7fd5
 status(host): add monitoring for didays.de and staging
012544344c
 public-reverse-proxy(host): add config for didays.de and staging
Compare 2 commits »
june created branch didays-de in CCCHH/ansible-infra 2026-07-09 22:18:33 +02:00