<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>pebble on The NNDI Blog</title><link>https://blog.nndi.cloud/tags/pebble/</link><description>Recent content in pebble 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/pebble/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><item><title>Using pebble to ship application logs to VictoriaLogs</title><link>https://blog.nndi.cloud/posts/using-pebble-to-send-logs-to-loki/</link><pubDate>Tue, 29 Jul 2025 00:00:00 +0000</pubDate><author>hello@nndi.cloud (NNDI)</author><guid>https://blog.nndi.cloud/posts/using-pebble-to-send-logs-to-loki/</guid><description>We migrated from using supervisor to having all our services managed by pebble. One of the benefits we got from switching is pebble&amp;rsquo;s native ability to ship logs to Loki or any other Loki compatible system. This capability allows us to run and collect logs from our services using one solution which is super convenient as it reduces one operational burden.
In this article, we will show how to configure pebble for shipping application logs to VictoriaLogs.</description></item><item><title>Why we switched from Supervisor to Pebble for running our services</title><link>https://blog.nndi.cloud/posts/switching-from-supervisor-to-pebble/</link><pubDate>Thu, 29 May 2025 00:00:00 +0000</pubDate><author>hello@nndi.cloud (NNDI)</author><guid>https://blog.nndi.cloud/posts/switching-from-supervisor-to-pebble/</guid><description>We recently completed a migration from supervisor to pebble on our production hosts.
In this article, we will share how we set it up, why we did so, and what we anticipate forward for our infrastructure moving forward.
At NNDI we build systems that typically run on Linux based operating systems, though we have also shipped Windows services as part of our Consulting Work. Most of our services are built with Go and so far we have taken advantage of Go&amp;rsquo;s ability to build single binaries to power our simple deployment pipeline which involves just taking the binary and putting it on the server.</description></item></channel></rss>