At Outlyer, as a monitoring company, we rely on time-series databases (TSDBs) as a foundation for building a scalable and reliable monitoring solution. Over the past few years, we’ve gone through 3…

File Transfer Protocol (FTP) is a network protocol used for transferring files between a client and a server on a computer network.

Vim is a powerful text editor with great capabilities. You can map multiple keys to perform different functionalities in Vim that makes your text editing eas...

Inviska Rename is a free and open source GUI batch file rename utility for Linux, Mac and Windows. It supports renaming based on music tags and Exif information, and much more.

A small tool that could store, version, retrieve, and format our application configurations in order to keep sync between coworkers and environments.

When it’s time to package up your Python application into a Docker image, the natural thing to do is search the web for some examples. And a quick search will provide you with plenty of simple, easy examples. Unfortunately, these simple, easy examples are often broken in a variety of ways, some obvious, some less so. To demonstrate just some of the ways they’re broken, I’m going to: Start with an example Dockerfile that comes up fairly high on some Google searches. Show how it’s broken. Give some suggestions on how to make it less broken. Note: Outside the specific topic under discussion, the Dockerfiles in this article are not examples of best practices, since the added complexity would obscure the main point of the article. Learn more about best-practices Docker images for Python.