I have the feeling that a blog post about distributing packages is needed. 😮 In a word filled with Containers, PaaS, and SaaS, it seems weird to talk about how we can automate the creation of Debian packages and APT repositories. Nonetheless, even if this appears to be a forgotten step for operations, some projects are not distributed over Debian packages, 👷♂️ and I need them for my Raspberry Pi! 😜
During the last year, I have been curious about Immutable Infrastructure. After researching, I noticed that I had been applying some of these concepts already to stateless Docker containers, and I wanted to do a practical project with it. So I thought about exploring Immutable Infrastructure and use it to deploy Hashicorp Vault.
During the last year I have learned how important it is to build, test and deploy using always the same docker container as well as reducing its size. As I have not found anything online, I want to remember and share it: I am testing my go packages with a multistage docker build inside my pipeline on GitLab. The odd way of testing go docker containers Especially when implementing CI best practices, I have seen projects running tests in different ways: