Engineering at Polyconseil

A technical insight into our staple food
  1. Deploy and use external-dns for Route53 in Kubernetes with Helm and Terraform

    As we migrate our SaaS apps to the AWS cloud, (and Kubernetes clusters specifically), it is imperative for us to be able to quickly deploy our applications, and to have a fully qualified domain name that doesn't change regardless of what happens to our resources. We tried a hack using a lambda function and tags, but it wasn't good enough. We looked at external-dns, and it appears to fulfill our needs, but no one on the Internet had shared their experiences with external-dns matching our needs. So I guess I'll be the first one to!

  2. Handling logs on AWS

    As we migrate our IT systems to the AWS cloud, it is imperative for us to be able to monitor their health and security. AWS does provide a range of tools for logging, however they feel fragmented and balky at times. Looking through logs in the dedicated AWS services was awkward at best, frustrating at worst, and definitely time-consuming. We needed a centralised, robust log storage and management infrastructure that we could control. So I built one!

  3. Usability and maintainability the LEGO way

    Scared of moving pieces in your applications?

    Wanna master usability like a piece of cake?

    Don't look further and come find some piece of mind.

  4. Migrating from json to jsonb

    How we migrated our PostgreSQL-based applications from text-formatted json to jsonb.

  5. Migrating from Ansible Tower to AWX

    For several years now, we used Ansible Tower to launch and manage our Ansible jobs. The GUI wasn't good and the software wasn't perfect, but it had some very important features for us. When RedHat bought Ansible, they multiplied our licence fee by 3. We told them everything that was wrong with Ansible Tower and paid for one more year. As we did not observed any improvement regarding our complains, we started to look elsewhere. When Redhat released an open source project around Ansible Tower codebase, we jumped in.

  6. SMTP as an API

    Using SMTP as a base protocol for machine or human API.

  7. Handling locks during database schema updates

    Database schema updates are inevitable. And we need to perform these updates while keeping the system up and responding. This can be a little scary at times, particularly when you remember this cloudy Tuesday when dozens of your customers called because everything seemed broken after running such a migration (I know you've been there too).

  8. Cross compiling with Schroot

    When you're dealing with embedded systems you will most likely need to cross compile software. Cross compiling and building on any computer or server can be a pain and the use of schroot is a good way to avoid them. We'll show a few examples of cross compiling software and finally we'll review how to do it with schroot and talk about pros and cons of this technique.

  9. Serious i18n text search

    Use Django, nece and PostgreSQL for serious internationalized text search and completion.

  10. Code your JS app like it's 86

    How to avoid rewriting your JavaScript application, thanks to older coding paradigms.

Page 1 / 2 »