nom3ad

Mistakes to Avoid: Docker Antipatterns

Whichever route you take to implementing containers, you’ll want to steer clear of common pitfalls that can undermine the efficiency of your Docker stack.

Don’t run too many processes inside a single container

The beauty of containers—and an advantage of containers over virtual machines—is that it is easy to make multiple containers interact with one another in order to compose a complete application. There is no need to run a full application inside a single container. Instead, break your application down as much as possible into discrete services, and distribute services across multiple containers. This maximizes flexibility and reliability.

Don’t install operating systems inside Docker containers

It is possible to install a complete Linux operating system inside a container. In most cases, however, this is not necessary. If your goal is to host just a single application or part of an application in the container, you need to install only the essential

nom3ad

Bookmarklets to use with GitHub!

By Gabriel Staples

TODO:

1. Look into this one: https://gist.github.com/juanca/669c59f15a17e20022b8bd78b12889e6.

References:

nom3ad

git filter-branch --tree-filter 'git ls-files -z | xargs -0 dos2unix' -- --all

nom3ad

# -*- coding: utf8 -*-
"""
A simple monkeypath for the pstats module to be able to see sub-millisecond timings

If display value is 0.000, display the time in microseconds
"""

import pstats

def f8(x):

nom3ad

/**
 * Example:
 *
 * <ng-container *rerender='changingInput'>
 *    this content will be re-rendered everytime `changingInput` changes
 * </ng-container>
 */

import { Directive,
         Input,

nom3ad

{
  "type": "object",
  "required": ["Statement"],
  "additionalProperties": false,
  "properties": {
    "Version": {
      "type": "string",
      "enum": ["2008-10-17", "2012-10-17"]
    },
    "Id": {

nom3ad

# GIT heart FZF
# -------------

is_in_git_repo() {
  git rev-parse HEAD > /dev/null 2>&1
}

fzf-down() {
  fzf --height 50% --min-height 20 --border --bind ctrl-/:toggle-preview "$@"
}

nom3ad

pipeline {
	agent {
		label 'jenkins-worker-light'
	}
    triggers {
        cron(env.BRANCH_NAME == 'master' ? '*/15 * * * *' : '')
    }
	options {
		timeout(time: 60, unit: 'SECONDS', activity: false)
	}

nom3ad

No, you are not allowed to change the copyright notice. Indeed, the license text states pretty clearly:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

But you are allowed to add a copyright notice.

If you want to keep the MIT license, which is what I would advise you to do, you only need to add a single line to the license file, before or after Copyright (c) 2012 Some Name with your own copyright notice. The final LICENSE file will look like this:

The MIT License (MIT)

nom3ad

@NonCPS
def parseJson(txt){
	def lazyMap = new groovy.json.JsonSlurper().parseText(txt)
	def map = [:]
	for ( prop in lazyMap ) {
    	map[prop.key] = prop.value
	}
	return map;
}