digitalcourage.social

BjörnManaged to built in <a href="https://mastodon.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a> manual as <a href="https://mastodon.social/tags/TexInfo" class="mention hashtag" rel="nofollow noopener" target="_blank">#TexInfo</a> Info manual. Just 4.7 MB Gzip compressed. It takes some time to load but it's better than the previous man 7 salt thou.

KungFuDiscoMonkeyUpdating My Salt Extensions <a href="https://paultraylor.net/blog/2025/updating-my-salt-extensions/" rel="nofollow noopener" translate="no" target="_blank">https://paultraylor.net/blog/2025/updating-my-salt-extensions/</a><a href="https://social.tsun.co/tags/packaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#packaging</a> <a href="https://social.tsun.co/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://social.tsun.co/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a>

KungFuDiscoMonkeyI've been using <a href="https://social.tsun.co/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a> for years, but slowly coming to the realization it might be time to move on. Not really a fan of <a href="https://social.tsun.co/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a> or <a href="https://social.tsun.co/tags/terraform" class="mention hashtag" rel="nofollow noopener" target="_blank">#terraform</a> so I'm not sure I would migrate to that. Reluctantly thinking it might be time to bite the bullet and properly give <a href="https://social.tsun.co/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k8s</a> a chance. Not a huge fan of verbose yaml everywhere, so there's a part of me that is tempted to write something higher level, that outputs to yaml (I know <a href="https://social.tsun.co/tags/helm" class="mention hashtag" rel="nofollow noopener" target="_blank">#helm</a> exists, but it also looks quite wordy (yamly?)) 🤔

Kevin Karhan :verified:<a href="https://mastodon.gamedev.place/@eniko" class="u-url mention" rel="nofollow noopener" target="_blank">@eniko</a> I mean, we don't even get fully-automated <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> where any "<a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>" could in theory perform as it's ripe for that.<ul><li>I mean, <a href="https://infosec.space/tags/automation" class="mention hashtag" rel="nofollow noopener" target="_blank">#automation</a> in <a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> exists, but noone's gonna drop <a href="https://infosec.space/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a>, <a href="https://infosec.space/tags/Puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Puppet</a> or <a href="https://infosec.space/tags/Saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Saltstack</a> (not even <a href="https://infosec.space/tags/Landscape" class="mention hashtag" rel="nofollow noopener" target="_blank">#Landscape</a> & <a href="https://infosec.space/tags/MAAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MAAS</a>) for <a href="https://infosec.space/tags/ChatGPT" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChatGPT</a> or similar bs.</li></ul><a href="https://infosec.space/tags/Protip" class="mention hashtag" rel="nofollow noopener" target="_blank">#Protip</a>: Ask "AI" fans if they would cobditionlessly entrust an "AI" with their financial details in full.<ul><li>Pretty shure none of them do.</li></ul>

rvstaverenGetting the feeling that <a href="https://mastodon.online/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a>, especially on <a href="https://mastodon.online/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> is getting more and more maintenance intensive. Disconnected minions, git pillar not loaded, upgrades seem problematic (and for that reason still at the 3006.x branch). Never had this with <a href="https://mastodon.online/tags/puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#puppet</a>…

__sharky__Today <a href="https://mastodon.social/tags/chatgpt" class="mention hashtag" rel="nofollow noopener" target="_blank">#chatgpt</a> told me this little trick , to make cmd.run idempotent in <a href="https://mastodon.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a>.<a href="https://mastodon.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> <a href="https://mastodon.social/tags/iac" class="mention hashtag" rel="nofollow noopener" target="_blank">#iac</a>

__sharky__Trying to create an <a href="https://mastodon.social/tags/immich" class="mention hashtag" rel="nofollow noopener" target="_blank">#immich</a> jail on <a href="https://mastodon.social/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#freebsd</a> let's see how it goes. Seems to be a nice <a href="https://mastodon.social/tags/picture" class="mention hashtag" rel="nofollow noopener" target="_blank">#picture</a> <a href="https://mastodon.social/tags/photo" class="mention hashtag" rel="nofollow noopener" target="_blank">#photo</a> <a href="https://mastodon.social/tags/sync" class="mention hashtag" rel="nofollow noopener" target="_blank">#sync</a> service. <a href="https://mastodon.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a>

xyhhx 🔻 (plz hire me)some project ideas i'm planning on working on in the near-mid future:- rewriting my qubes os config as salt states, then offering them as rpm packages. i have some nice stuff in here! - making a foss alternative to those cringey resume makers. it supports json resume schema - working on an actually good alternative to nextcloud and cryptpad <a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubes</a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubesOS</a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltStack</a> <a href="https://nso.group/tags/cryptpad" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptpad</a> <a href="https://nso.group/tags/nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#nextcloud</a> <a href="https://nso.group/tags/resume" class="mention hashtag" rel="nofollow noopener" target="_blank">#resume</a> <a href="https://nso.group/tags/jsonResume" class="mention hashtag" rel="nofollow noopener" target="_blank">#jsonResume</a>

xyhhx 🔻 (plz hire me)it's been a while since i complained about salt stacki hate salt stack<a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltStack</a> <a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubes</a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubesOS</a>

Qubes Users Berlin🌟 To all Qubes OS enthusiasts! 🌟Continuing from our last meetup this Friday, we're diving into the exciting topics of Salt and Android in Qubes OS! 🎉 (see our homepage 🌐 )Before we get started, we want to hear from YOU – whether you're based in Berlin or anywhere else in the world!How have you incorporated Salt into your Qubes setup? What are your use cases? Share your experiences and let's learn from each other! 🌞 <a href="https://mastodon.social/tags/QubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#QubesOS</a> <a href="https://mastodon.social/tags/SaltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#SaltStack</a> <a href="https://mastodon.social/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://mastodon.social/tags/ShareYourUseCase" class="mention hashtag" rel="nofollow noopener" target="_blank">#ShareYourUseCase</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

xyhhx 🔻 (plz hire me)i'm making my salts for my qubes set up distributable as rpms, which is also a convenient way to transfer them from domUs to dom0 in a more secure manner (since the rpms are signed)what i'm unsure of is this: currently, i have one rpm that is my whole repo, and the repo contains topfiles that a user can enable individually. should i instead offer the vms (or bundles of them, in some cases) as individual rpms?<a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubes</a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubesOS</a> <a href="https://nso.group/tags/salt" class="mention hashtag" rel="nofollow noopener" target="_blank">#salt</a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltStack</a> <a href="https://nso.group/tags/rpm" class="mention hashtag" rel="nofollow noopener" target="_blank">#rpm</a>

xyhhx 🔻 (plz hire me)on the topic of salt states for qubes, i found this extremely cool repo: <a href="https://github.com/gonzalo-bulnes/qubes-mgmt-salt-user" rel="nofollow noopener" translate="no" target="_blank">https://github.com/gonzalo-bulnes/qubes-mgmt-salt-user</a>brilliant way to organize the salts and distribute them imo<a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubes</a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubesOS</a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltStack</a>

xyhhx 🔻 (plz hire me)calling all qubes users who use salt! is there a way to target domUs with `state.highstate` when using many topfiles? my repo is at <a href="https://git.sr.ht/~xyhhx/qubes-salts" rel="nofollow noopener" translate="no" target="_blank">https://git.sr.ht/~xyhhx/qubes-salts</a>(details in reply)<a href="https://nso.group/tags/qubes" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubes</a> <a href="https://nso.group/tags/qubesOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubesOS</a> <a href="https://nso.group/tags/salt" class="mention hashtag" rel="nofollow noopener" target="_blank">#salt</a> <a href="https://nso.group/tags/saltStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltStack</a>

Brad L. :verified:Dear <a href="https://hachyderm.io/tags/LazyWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#LazyWeb</a> / <a href="https://hachyderm.io/tags/lazyfedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#lazyfedi</a>,I'm new to <a href="https://hachyderm.io/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k8s</a> and am wondering how to handle templating large amounts of config files. I couldn't find anything super useful in my search so I have an <a href="https://hachyderm.io/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> sidecar I run to generate the kustomizations and config files. My most recent Ansible change was 30 lines, it resulted in changing 5,000 lines of YAML which will further be fed to Kustomize.There has to be a better way?I've heard about Helm, Yoke, KRO, and using an operator pattern. My understanding of those options is:* Helm - My Org recommends avoiding (I don't know why) * KRO - Not stable, but FFS neither is Kustomize * Yoke - Almost kinda operator pattern * Operator Pattern - This feels like reinventing a fucking config manager (ala <a href="https://hachyderm.io/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a>, <a href="https://hachyderm.io/tags/Puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Puppet</a>, <a href="https://hachyderm.io/tags/Chef" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chef</a>, <a href="https://hachyderm.io/tags/Saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Saltstack</a>) for every fucking project. What new hell this is.I'm hoping I'm missing something because the only workable flow for this workload is: 1) Create ansible roles/playbook to generate the kustomization.yaml and resources 2) Generate those kustomizations, check them into git 3) Use Kustomize via GitOps to expand the YAML even more 4) Push a metric fuckton of YAML to productionI'm losing my mind over here.

__sharky__I am a long time <a href="https://mastodon.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a> user . Never used salt-formulas , but recently I found this documentation . <a href="https://github.com/saltstack-formulas/template-formula/blob/master/docs/TOFS_pattern.rst" rel="nofollow noopener" translate="no" target="_blank">https://github.com/saltstack-formulas/template-formula/blob/master/docs/TOFS_pattern.rst</a> <a href="https://github.com/saltstack-formulas/template-formula/blob/master/docs/map.jinja.rst" rel="nofollow noopener" translate="no" target="_blank">https://github.com/saltstack-formulas/template-formula/blob/master/docs/map.jinja.rst</a> Wow , that is so good , it should be in the official docs . <a href="https://mastodon.social/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> <a href="https://mastodon.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> <a href="https://mastodon.social/tags/iac" class="mention hashtag" rel="nofollow noopener" target="_blank">#iac</a>

Kevin Karhan :verified:<a href="https://bsd.network/@sizeofvoid" class="u-url mention" rel="nofollow noopener" target="_blank">@sizeofvoid</a> I'd rather wish for good <a href="https://infosec.space/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a> support of <a href="https://infosec.space/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a> as well as other orchestration tools like <a href="https://infosec.space/tags/fleetdm" class="mention hashtag" rel="nofollow noopener" target="_blank">#fleetdm</a>, <a href="https://infosec.space/tags/Landscape" class="mention hashtag" rel="nofollow noopener" target="_blank">#Landscape</a>, <a href="https://infosec.space/tags/puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#puppet</a> and <a href="https://infosec.space/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a>...

folken<a href="https://infosec.exchange/@paulsanders" class="u-url mention" rel="nofollow noopener" target="_blank">@paulsanders</a> yeah suddenly that <a href="https://chaos.social/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a> cluster with <a href="https://chaos.social/tags/ceph" class="mention hashtag" rel="nofollow noopener" target="_blank">#ceph</a> and <a href="https://chaos.social/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#zfs</a> running <a href="https://chaos.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://chaos.social/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#kubernetes</a> for running stuff such as <a href="https://chaos.social/tags/nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#nextcloud</a> <a href="https://chaos.social/tags/matrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#matrix</a> <a href="https://chaos.social/tags/dex" class="mention hashtag" rel="nofollow noopener" target="_blank">#dex</a> of course all managed with <a href="https://chaos.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> principles <a href="https://chaos.social/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> ified in <a href="https://chaos.social/tags/forgejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#forgejo</a> with <a href="https://chaos.social/tags/argocd" class="mention hashtag" rel="nofollow noopener" target="_blank">#argocd</a> and all managed by <a href="https://chaos.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a> seems completley justified.

Björn<a href="https://troet.cafe/@simondeutschl" class="u-url mention" rel="nofollow noopener" target="_blank">@simondeutschl</a> Habs auch vor ein paar Jahren gemacht. Sobald man drin ist in der Sache ist alles weitere sehr recht einfach, es kommt natürlich. Was ich direkt empfehle ist Konfiguration in Versions-Kontrolle z.B. git zu halten so ist es viel einfacher Übersicht zu halten. Gleiches gilt wenn es um Probleme geht, am besten todo listen machen. Das nächste Level ist dann alles deklarativ zu machen z.B. mit <a href="https://mastodon.social/tags/Saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Saltstack</a>. Es kompliziert das ganze aber auf lange sicht kann es vieles vereinfachen.

Freifunk Frankfurt a.M.Free and Open Source Infra and Software <a href="https://chaos.social/tags/Hackathon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hackathon</a> Wir laden euch zum gemeinsamen Arbeiten an <a href="https://chaos.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> in den <a href="https://chaos.social/@cccffm" class="u-url mention" rel="nofollow noopener" target="_blank">@cccffm</a> vom 17.–19. Januar 2025 ein.Pretix: <a href="https://pretix.ffffm.net/ffffmev/hackathon202401/" rel="nofollow noopener" translate="no" target="_blank">https://pretix.ffffm.net/ffffmev/hackathon202401/</a>Raum zum Entwickeln und Austauschen bezüglich Freier und Offener <a href="https://chaos.social/tags/Infrastruktur" class="mention hashtag" rel="nofollow noopener" target="_blank">#Infrastruktur</a> und Software. Zum Beispiel Entwicklung an <a href="https://chaos.social/tags/OpenWrt" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenWrt</a>, der Umbau von <a href="https://chaos.social/tags/Saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Saltstack</a> oder <a href="https://chaos.social/tags/Puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Puppet</a> auf <a href="https://chaos.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NixOS</a> oder <a href="https://chaos.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a>, genauso aber auch Dokumentationserweiterung oder das Erstellen von Anleitungen fürs Routing im Internet<a href="https://chaos.social/tags/Freifunk" class="mention hashtag" rel="nofollow noopener" target="_blank">#Freifunk</a> <a href="https://chaos.social/tags/Frankfurt" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frankfurt</a>

folken<a href="https://infosec.exchange/@paco" class="u-url mention" rel="nofollow noopener" target="_blank">@paco</a> <a href="https://chaos.social/tags/nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#nextcloud</a> has a history refusing to package its software. And refusing to work with distro maintainers.Appimages are useless for the reasons you mentioned.My nextcloud instance uses the offical docker image which I manage using a <a href="https://chaos.social/tags/saltstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#saltstack</a> state to keep it current.The clients get the snap package. Also salt managed. This setup has worked beautifully so far.It can be that the client lags behind, but sofar I havent had any problems, as I also use the stable docker image.

Recent searches

Search options

Administered by:

Server stats:

#saltstack