Various Ways of Restarting Docker Containers

When running docker containers, it’s important to be aware that both the container and server can crash at any time. When either of these events occur, containers are not automatically brought back up. If running Docker on a single host, the –restart flag can be passed in as an option to the docker run command. docker run --restart=always image This should cause the container to restart when a crash happens. If running docker in a swarm cluster, there is a new experimental feature in Docker Swarm 1.1 that will rebalance containers. »

Windows vs Unix-Like Filesystems and Git

Introduction A debonair uses the right tool for the job and has no trouble switching between Windows, Mac, and Linux. However moving between different operating systems has its own share of issues, especially when in comes to how files are handle. Filesystem Differences In secure computing, a file has permissions which control who can read, write, and execute the file. Mac OS and other unix-like variants have separate file modes for each of those actions. »

Brandon Chothia

Database Collation

Background I was having an interesting discussion with some fellow debonairs regarding database normalization. The discussion took a technical turn and we got on the topic of whether an integer search in a database is faster than a string search. I took a stroll down memory lane and I remember my database professor mentioning that integer searches are faster, but I could not remember why. A google search revealed this article on StackOverflow. »

Complete guide to continuous deployment to maven central from Travis CI

Continuous deployment is a very useful tool, especially for open source projects. Commonly the people in an open source project accepting pull requests might not all have the permissions or skills to also deploy those changes, but with continuous deployment they don’t need to. Once code is accepted into the master branch it is deployed automatically. This allows for agile features and bugfixes without taking up the time of the few individuals doing the deploying. »

The Debonair Stack - Part 1 : Introduction

“A debonair must know the entire stack.” - wise man. A software stack is quite an abstract thought. You can think of it as a set of programs that work together to produce an end result. For example, the end result of this, is a website. Whatever components are needed for this website to run are what make up its stack. In this case, the stack consists of Ghost, node.js, and docker. »