MastodonTech.de

It's Richie<a href="https://hachyderm.io/tags/CommunityHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityHosting</a> <a href="https://hachyderm.io/tags/Ops" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ops</a> A small group of us are working on community level hosting of 'self-hosted' FOSS tools (think <a href="https://hachyderm.io/tags/NextCloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#NextCloud</a> and more) setup as a local service offering for local grassroots organisations. We're seeking advice/tips/guidance.We're keen to do some orchastration but want to avoid the complexity of say Kubernetes.As a start we were looking at Ansible with Docker Swarm but we're now exploring other alternatives.Anyone have experience at this sort of hobbist just a bit bigger than <a href="https://hachyderm.io/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a> Ops scale?<a href="https://hachyderm.io/tags/Pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pyinfra</a> is being considered as an Ansible, in the projects words "Think ansible but Python instead of YAML, and a lot faster." (<a href="https://pyinfra.com" rel="nofollow noopener" translate="no" target="_blank">https://pyinfra.com</a>)Anyone have experience at this homelab/small hosting level? Would love any tips/suggestions for tools/approaches.One source of inspiration is the 12Factor app methodology: <a href="https://12factor.net" rel="nofollow noopener" translate="no" target="_blank">https://12factor.net</a>Personally, as a rubyist I'm always keen to know what the ruby community is doing in this space also. Haven't seen many others doing work at this scale, lets use the tag <a href="https://hachyderm.io/tags/CommunityHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityHosting</a> to keep connected :)<a href="https://adlsolarpunk.net/@digital_justice_society" class="u-url mention" rel="nofollow noopener" target="_blank">@digital_justice_society</a>cc: <a href="https://hachyderm.io/@jadehopepunk" class="u-url mention" rel="nofollow noopener" target="_blank">@jadehopepunk</a> <a href="https://hachyderm.io/@ryan" class="u-url mention" rel="nofollow noopener" target="_blank">@ryan</a> @gilbert @bounding_star <a href="https://hachyderm.io/@steph" class="u-url mention" rel="nofollow noopener" target="_blank">@steph</a> <a href="https://mastodon.online/@moxvallix" class="u-url mention" rel="nofollow noopener" target="_blank">@moxvallix</a> <a href="https://adlsolarpunk.net/@organvoid" class="u-url mention" rel="nofollow noopener" target="_blank">@organvoid</a> <a href="https://aus.social/@teq" class="u-url mention" rel="nofollow noopener" target="_blank">@teq</a> <a href="https://hachyderm.io/tags/CommunityHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityHosting</a> <a href="https://hachyderm.io/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://hachyderm.io/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://hachyderm.io/tags/ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#ruby</a> <a href="https://hachyderm.io/tags/RubyOnRails" class="mention hashtag" rel="nofollow noopener" target="_blank">#RubyOnRails</a> <a href="https://hachyderm.io/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://hachyderm.io/tags/Orchastration" class="mention hashtag" rel="nofollow noopener" target="_blank">#Orchastration</a> <a href="https://hachyderm.io/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://hachyderm.io/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenTofu</a> <a href="https://hachyderm.io/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://hachyderm.io/tags/SelfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosted</a>

scyThe idea of <a href="https://chaos.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> is great. The execution however …Let's just say, I would've done a few things in a different way.

dereulenspiegelIs it crazy to put pyinfra code into a <a href="https://chaos.social/tags/Nix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nix</a> derivation to handle configuration of things like PostgreSQL (creating users etc.)? <a href="https://chaos.social/tags/Nix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nix</a> itself kinda sucks at managing state of services and <a href="https://chaos.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> looks quite nice for that.

scyIn the <a href="https://chaos.social/tags/Hetzner" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hetzner</a> Cloud API, you can refer to resources by their ID (an integer) or their name. Both are unique. The name is user-defined and designed to be human-readable, but needs to be identifier-like.For example, you'd name a server "db01" or a volume "db-main" or an IP address "db01-v6".However, in <a href="https://chaos.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a>, "name" is a reserved word and I can't use it, but "id" is something else, too.For now I've used "handle" instead of "name", but I wonder whether you have better suggestions.

scyWait, neither <a href="https://chaos.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> nor <a href="https://chaos.social/tags/BundleWrap" class="mention hashtag" rel="nofollow noopener" target="_blank">#BundleWrap</a> run actual Python code on the remote hosts, right? They're apparently both basically just fancy wrappers for running shell commands, mainly via SSH.In contrast, <a href="https://chaos.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> _does_ run Python on the remote side. Which means that Python is required to be installed, but also means that you can do more sophisticated stuff than parsing CLI tool output. 🤔

dilawar<a href="https://fosstodon.org/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> is good, almost great! Give it a try.Nothing against <a href="https://fosstodon.org/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a> but its nice to write <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> over markup/text.```bash uvx pyinfra -y -vvv \ @ssh/gitlab \ --data ssh_key=~/.ssh/dilawar-ap-south-1.pem \ --data ssh_user=ec2-user \ operations/update_gitlab.py ```

Jeff ToonEine Frage an die PyInfra-Admins hier im fediverse. Ich hab mich in den letzten Tagen mit diesem Tool beschäftigt und so einige deploy-scripte geschrieben. Nun komme ich an Punkte, wo ich nicht sicher bin, ob das, was ich gerade mache, so im Sinne des Erfinders ist.Ich möchte ein paar Server (6 - 10) per pyinfra einrichten. Dabei werden einige Server komplette Webserver mit PHP, PHP-FPM, diversen WebApps (Nextcloud, CMS, WIKI, etc.) und einige bekommen nur einen VPN-Server. Das ist so ganz grob mein Ziel.Ich bin so weit, dass PyInra mir den kompletten Server aufsetzt. Von der statischen IP, ein paar Anpassungen an der .bashrc, den SSH-Port ändert, Apache, LetsEncrypt, fail2ban, php, php-fpm (beides für verschiedene php-versionen) usw. alles installiert. Toll!Jetzt bin ich garde dabei, ein Deploy-Script zu schreiben, das mir die Umgebung für eine WebApp einrichtet: vhost.conf für die Domain erstellen und konfigurieren, User, Gruppe, HomeDirs, LogDirs usw. erstellen, LetsEncrypt-Zertifikate holen, usw.Danach sollen dann all die WebApps (also zum Beispiel nextcloud) per deploy-script installiert werden.Das sieht alles schon ziemlich gut aus und ich kann mir vorstellen, wie das alles zusammen spielen wird. Aber es ist noch ein weiter Weg.Mein Problem ist gerade, dass mein Inventory-Script allein nur für einen Host in Kürze bei etwa 200 Zeilen an Host-Data Umfang hat. Ich habe die Befürchtung, dass ich bei dem Umfang an Parametern den Überblick verliere und Fehler mache. Wenn man nur mit dem simplen Dictonary von Python arbeitet, kann man leicht einen Fehler machen, wenn man einen Key angibt und sich dabei vertippt. Es gibt ja keine Fehlerkorrektur oder ein Check, dass der Name des Keys richtig geschrieben wurde. Oder man vergisst einen Eintrag im Dictonary - also in der Beschreibung des Hostes - vorzunehmen. Und dann fliegt hinterher alles auseinander. Ich bin nun dabei, eigene Klasse für die Hosts, Apps und so weiter zu erstellen und dafür zu sorgen, dass dort alles korrekt ist. Aber das ist eine riesige Menge an Arbeit, die mal nicht in 2 Tagen erledigt scheint.Ist das sinnvoll? Ist das der richtige Weg? Wie handhabt ihr das? <a href="https://mastodon.online/users/robertmx" class="u-url mention" rel="nofollow noopener" target="_blank">@robertmx</a> <a href="https://linux.community/c/linux" class="u-url mention" rel="nofollow noopener" target="_blank">@linux</a> <a href="https://friendica.opensocial.space/search?tag=pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> <a href="https://friendica.opensocial.space/search?tag=linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://friendica.opensocial.space/search?tag=administration" class="mention hashtag" rel="nofollow noopener" target="_blank">#administration</a> <a href="https://friendica.opensocial.space/search?tag=it" class="mention hashtag" rel="nofollow noopener" target="_blank">#it</a>

Jeff ToonWer hat Ahnung von PyInfra? Ich arbeite mich da gerade rein und bin eigentlich ziemlich angetan. Abgesehen davon, dass ich ständig bei meinen Suchanfragen im Netz auf Tipps zu alten Versionen stoße, die dann meist nicht funktioniert 🙁Ich würde zum Beispiel aktuell gern wissen, wie ich die Existenz einer Datei auf dem Server prüfen kann, wenn die Datei nur mit root-Rechten zu sehen ist. Ein "_sudo=True" kann man nicht überall einbauen. Auch das globale "_sudo=True" scheint nicht zu helfen.Also irgendwas der Art:<blockquote>myfile = host.get_fact( File, "/root/.bashrc", )</blockquote> Hat da einer eine Idee?<a href="https://friendica.opensocial.space/search?tag=pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> <a href="https://friendica.opensocial.space/search?tag=Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://linux.community/c/linux" class="u-url mention" rel="nofollow noopener" target="_blank">@linux</a>

David Zaslavsky<a href="https://frankfurt.social/@malte" class="u-url mention" rel="nofollow noopener" target="_blank">@malte</a> 😂 I have also been looking into pyinfra lately. If nothing else, it's that much less code I have to write in YAML and that's a win.<a href="https://techhub.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://techhub.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> <a href="https://techhub.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a>

MalteIt's this time of year again where I think about replacing ansible with something else.This year it's pyinfra.Funny side note: macos wants to replace ansible with unusable. :D<a href="https://frankfurt.social/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a> <a href="https://frankfurt.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a>

robertmx* The selfhosting docs on deltachat are somewhat rudimentary. Theres a github repo and some <a href="https://mastodon.online/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> scripts, but compared to <a href="https://mastodon.online/tags/synapse" class="mention hashtag" rel="nofollow noopener" target="_blank">#synapse</a> and <a href="https://mastodon.online/tags/xmpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xmpp</a>, the docs are less sophisticatedIn conclusion I would recommend <a href="https://mastodon.online/tags/xmpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xmpp</a> for a closed organizational messaging due to LDAP integration and "enterprise" features and delta chat for nontechnical communication (if you can live without video / audio).3/3

David Zaslavsky<a href="https://mastodon.social/@sumanthvepa" class="u-url mention" rel="nofollow noopener" target="_blank">@sumanthvepa</a> For everything you want to do, I'm pretty sure you'll have to do a lot of custom coding regardless of how you do it, but you could check out <a href="https://techhub.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> which is like a more lightweight version of Ansible. Or I should say, it's a lighter-weight tool that tries to do the same thing Ansible does (basically, scripting but optimized for configuring systems). I don't know if it will actually make your job easier, I'm just suggesting it's worth a quick look to see.

David Zaslavsky<a href="https://social.linux.pizza/@nebucatnetzer" class="u-url mention" rel="nofollow noopener" target="_blank">@nebucatnetzer</a> I'm working on it, for my personal infrastructure. It is wayyyy more pleasant (and efficient) to be writing code in an actual programming language instead of in YAML, but the tradeoff is losing access to Ansible's huge library of tasks and roles. So you wind up having to implement more things yourself in pyinfra. Personally, I think it's well worth it so I will continue to plug away with pyinfra, but I can see how someone who's working on a large body of infrastructure and has limited time might consider it not viable.<a href="https://techhub.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://techhub.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> <a href="https://techhub.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a>

Alejandro Baez<a href="https://social.linux.pizza/@Zer0Rank" class="u-url mention" rel="nofollow noopener" target="_blank">@Zer0Rank</a> <a href="https://social.linux.pizza/@nebucatnetzer" class="u-url mention" rel="nofollow noopener" target="_blank">@nebucatnetzer</a> as for if I would do it again? Definitely! I wrote so many ansible modules in my day. But a lot qas due to the only tool that made the least trade offs for me. Ansible now over a decade old and for all its capabilities, a lot of the cuts are all still there with it.<a href="https://fosstodon.org/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> feels fresh. You can also get very far depending on how well you know the language. Ansible is more of learn how to code in yaml and jinja REALLY well. 🫠

Serge from BabkaSetting up Podman with PyInfra, I keep thinking "I should make this a PyInfra module", but if I do that now, I'll never get to my goal.<a href="https://babka.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://babka.social/tags/Devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#Devops</a> <a href="https://babka.social/tags/Podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Podman</a> <a href="https://babka.social/tags/PyInfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyInfra</a> <a href="https://babka.social/tags/ADHD" class="mention hashtag" rel="nofollow noopener" target="_blank">#ADHD</a>

Alejandro BaezI discovered <a href="https://fosstodon.org/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a>, and now I want to use it. It's like skipping using <a href="https://fosstodon.org/tags/yaml" class="mention hashtag" rel="nofollow noopener" target="_blank">#yaml</a> in <a href="https://fosstodon.org/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a>. Similar to <a href="https://fosstodon.org/tags/fabric" class="mention hashtag" rel="nofollow noopener" target="_blank">#fabric</a>, but less low level. 😅With pyinfra, you still have things like ansible roles abstractions. But you write your roles all in <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>. 😎 All I know is here I go again with this rabbit hole. 🫠<a href="https://docs.pyinfra.com/en/3.x/getting-started.html" rel="nofollow noopener" translate="no" target="_blank">https://docs.pyinfra.com/en/3.x/getting-started.html</a>

Wesley MooreNew post: <a href="https://www.wezm.net/v2/posts/2024/tiny-cdn/" rel="nofollow noopener" translate="no" target="_blank">https://www.wezm.net/v2/posts/2024/tiny-cdn/</a>I built a tiny CDN for my website to reduce the latency for visitors in different parts of the world.<a href="https://mastodon.decentralised.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.decentralised.social/tags/ChimeraLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChimeraLinux</a> <a href="https://mastodon.decentralised.social/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a>

robertmx<a href="https://fosstodon.org/@RyuKurisu" class="u-url mention" rel="nofollow noopener" target="_blank">@RyuKurisu</a> <a href="https://social.mei-home.net/@mmeier" class="u-url mention" rel="nofollow noopener" target="_blank">@mmeier</a> The strengths of <a href="https://mastodon.online/tags/K8S" class="mention hashtag" rel="nofollow noopener" target="_blank">#K8S</a> (autoscaling, rebalancing, self-healing) were not terribly relevant to my homelab.The disadvantages (high resource usage and complexity) started bothering me. I had some machines idling at 20% CPU just for all the management processes.I went on to orchestrate the <a href="https://mastodon.online/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> with <a href="https://mastodon.online/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansible</a> / <a href="https://mastodon.online/tags/pyinfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyinfra</a> and used plain old <a href="https://mastodon.online/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> containers. That massively reduced complexity, load, traffic and WTF moments (spent days hunting bugs in the flannel CNI).

Serge from BabkaI've written a blog post about choosing a configuration management system. Let me know your thoughts!<a href="https://blog.emacsen.net/blog/2024/09/29/sysadmin-config-management/" rel="nofollow noopener" translate="no" target="_blank">https://blog.emacsen.net/blog/2024/09/29/sysadmin-config-management/</a><a href="https://babka.social/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a> <a href="https://babka.social/tags/ConfigurationManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#ConfigurationManagement</a> <a href="https://babka.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> <a href="https://babka.social/tags/ops" class="mention hashtag" rel="nofollow noopener" target="_blank">#ops</a> <a href="https://babka.social/tags/Puppet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Puppet</a> <a href="https://babka.social/tags/CFengine" class="mention hashtag" rel="nofollow noopener" target="_blank">#CFengine</a> <a href="https://babka.social/tags/Chef" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chef</a> <a href="https://babka.social/tags/PyInfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyInfra</a> <a href="https://babka.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a>

Serge from BabkaPyInfra demonstrates a powerful point. With Ansible if you want to feed information to Ansible, you must do through so Yaml. Yaml is fine, but PyInfra simply lets you feed information directly to it without an intermediary file format.Why do we complicate our lives with these intermediate formats when they're often unnecessary? Wouldn't pure programming be better for the user?I'm looking at you, OpenTofu.<a href="https://babka.social/tags/PyInfra" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyInfra</a> <a href="https://babka.social/tags/Yaml" class="mention hashtag" rel="nofollow noopener" target="_blank">#Yaml</a> <a href="https://babka.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://babka.social/tags/DSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#DSL</a> <a href="https://babka.social/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenTofu</a> <a href="https://babka.social/tags/Terraform" class="mention hashtag" rel="nofollow noopener" target="_blank">#Terraform</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#pyinfra