<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ansible on The NNDI Blog</title><link>https://blog.nndi.cloud/tags/ansible/</link><description>Recent content in ansible on The NNDI Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>hello@nndi.cloud (NNDI)</managingEditor><webMaster>hello@nndi.cloud (NNDI)</webMaster><lastBuildDate>Tue, 03 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.nndi.cloud/tags/ansible/index.xml" rel="self" type="application/rss+xml"/><item><title>Automated Go Deployments with GitHub Actions, Ansible and Pebble</title><link>https://blog.nndi.cloud/tutorials/2026/automated-go-deployments-with-github-actions-ansible-and-pebble/</link><pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate><author>hello@nndi.cloud (NNDI)</author><guid>https://blog.nndi.cloud/tutorials/2026/automated-go-deployments-with-github-actions-ansible-and-pebble/</guid><description>We&amp;rsquo;ve recently started bringing Ansible into our deployment pipeline — and it&amp;rsquo;s changed how we think about shipping. No more SSHing into servers and running commands by hand. No more wondering which version is actually running. Push a tag, and it goes.
This post walks through the exact setup: a Go app, a VPS, and a pipeline where GitHub Actions builds your binary, Ansible deploys it, and Pebble manages the running service.</description></item></channel></rss>