For traffic, we do have a single repository. And especially now we do have some plaggings in traffic vi too. So yes, it's a singular repo, i guess. Do you do any repose tinking, anything like that, behind the scene so that you centralize all the issues in a single place? Or do you just open issues, for example, for gain, in the pluggand repo, and then you have a view that merges them al together? How does that look? Yes, every repo has their own issues. Between different repos so traffic is having its own issues relating another issue on another repo, sometimes on another project. Maybe even that
Transcript
chevron_right
Play full episode
chevron_right
Transcript
Episode notes
This week Emile Vauge, founder & CEO of Traefik, joins Gerhard to share a story that started as a solution to a 2000 microservices challenge, the real-world implications of shipping many times a day for years, and the difficulties of sustaining an inclusive and healthy open-source community while building a product company.
Working every day on keeping the open-source community in sync with the core team was an important lesson. The second learning was around big changes between major versions.
The journey from Travis CI to Circle CI, then to Semaphore CI and eventually GitHub Actions is an interesting one. The automation tools inspired by the Mymirca ant colony is a fascinating idea, executed well. There is more to discover in the episode.
Changelog++ members get a bonus 1 minute at the end of this episode and zero ads. Join today!
Sponsors:
Render – The Zero DevOps cloud that empowers you to ship faster than your competitors. Render is built for modern applications and offers everything you need out-of-the-box. Learn more at render.com/changelog or email changelog@render.com for a personal introduction and to ask questions about the Render platform.
Sentry – Working code means happy customers. That’s exactly why teams choose Sentry. From error tracking to performance monitoring, Sentry helps teams see what actually matters, resolve problems quicker, and learn continuously about their applications - from the frontend to the backend. Use the code SHIPIT and get the team plan free for three months.
LaunchDarkly – Ship fast. Rest easy. Deploy code at any time, even if a feature isn’t ready to be released to your users. Wrap code in feature flags to get the safety to test new features and infrastructure in prod without impacting the wrong end users.
Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com
