Carlos Becker

GoReleaser’s journey begins in December 21, 2016: the day I made its very first commit.

Shared some tips about managing medium-sized OpenSource projects.

I wanted to set up a fault tolerant nats-streaming-server, but couldn’t find a “quick” guide on how to do it - so here we are.

Quick tip to improve the docker build speed using go modules.

I wanted to set up a high available nats-streaming-server cluster, but couldn’t find a “quick” guide on how to do it.

Often I need to “do X only if files on some folder changed” or whatever.

The next GoReleaser version will have a more flexible Docker configuration format.

Caching things can be hard to do and hard to test.

I have written some exporters to observe things on GitHub.

Ever wanted to validate your Packer image with Goss?

I’m working in a project that uses Chef, so it has a lot of JSON files.

I shared some of my experiences coding GoReleaser, this time, more about community and less about Go itself.

GoReleaser was able to build Snapcraft packages for a long time, but it wasn’t able to push them until today.

I have an old Couchbase 4.5.x cluster, and I thought it would be nice to upgrade it.

A quick review of my second ever GopherCon - the first one as a speaker, and my experience talking.

Migrating an ElasticSearch cluster from version 2 to 5 can be challenging, even more if it is a big cluster.

I’ve started GoReleaser almost 2 years ago.

It has been one month since I started working fully remote, and I think I learned some things I can share.

I like to keep my GitHub clean.

I wanted to set up a prometheus machine for me to monitor random stuff, but I was always postponing that because I didn’t want to use SSH port-forwarding, firewalls, create a VPC and/or setup an OpenVPN server or anything like that.

Everything in life eventually comes to an end, including life itself.

When I first announced GoReleaser roughly 1 year ago, on January 2017, I never thought it would be somewhat famous.

Over the years I read several articles on how to be effective, and how the 10x engineer thing is or is not a lie and all that.

After some time, I finally decided to move my blog from Jekyll to Hugo.

It was the Go 1.10 Release party - my talk was about what changed in Go 1.10.

I’ve been working on GoReleaser for more than a year now, and one of the things that was bothering me the most was fpm.

I spoke about how we migrate our monitoring infrastructure to Prometheus & Friends, what we got out of it and how it is working for us right now.

I showed how to build and release binaries in Go, including cross-compiling, Docker images, Linux packages and Homebrew, featuring GoReleaser on the end.

This past weekend I decided I need to clean up my GitHub profile.

I always wanted to know how stargazers of my repos increased over time.

I’ve been working with DigitalOcean, Heroku and AWS for some years now.

I’ve been using Jekyll on my blog since 2012.

We are running Kubernetes on both sandbox and production for some months now.

Last few months I’ve been using Go to write quite a lot of tools.

Microservices is the new fancy way of doing applications.

At ContaAzul, we use the CI infrastructure a lot.

At ContaAzul, we have several old pieces of code that are still running in production.

I have some apps written in Go, which I deliver as binaries for each platform using GitHub releases.

Watchub is a service that notifies you of people who followed/unfollowed you and starred/unstarred your repositories.

As a DevOps/SRE, I spent a reasonable amount of time dealing with metrics and alerts.

I have seen a lot of posts like this subject, but almost all of them were about stuff you should do and almost none of them reflected how I truly feel, how I want a product to be so I can “love” it.

Every now and then an active java-based project enters a “dependency hell” state.

I’ve lost a considerable amount of time trying to bind those things together, so I decided to write this quick post about it, so others could also benefit from it.

This is the story on how I sped up my terminal load time.

booleans, am I right?

I’ve been wanting to write this for a long time, just to clarify my thoughts on the subject.

This is just a quick overview of how I did it in antibody’s homepage.

I gave a little intro on Docker and talked about when to use it or not.

In Go, it’s dead simple to get the value from an environment variable:

Or: how to ship your app in a <20Mb container.