Carlos Alexandre calexandrepcjr

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

The PATH is an important concept when working on the command line. It's a list of directories that tell your operating system where to look for programs, so that you can just write script instead of /home/me/bin/script or C:\Users\Me\bin\script. But different operating systems have different ways to add a new directory to it:

Windows

The first step depends which version of Windows you're using:

If you're using Windows 8 or 10, press the Windows key, then search for and

Hexagonal Architecture - Message-Oriented Software Design por Matthias Noback

Qual é o problema com a arquitetura das aplicações atuais?
Um projeto, na maioria das vezes, é começado pequeno, por uma pessoa e sem saber como será a sua evolução.
Pode acontecer de novas pessoas entrarem no projeto e não conhecerem as regras que guiam a aplicação.
Um dos princípios de organização é o MVC ou Model View Controller.
No MVC a regra de negócio fica na Model, os templates na View e a mediação é feita pelo Controller.
O MVC não é suficiente para manter uma aplicação com código compreensível durante muito tempo.
A ideia de utilizar MVC veio de frameworks e a maioria das aplicações estão acopladas de alguma maneira a frameworks.
Um projeto é iniciado normalmente (1) escolhendo um framework, (2) instalando um esqueleto, (3) removendo códigos de demonstração, (

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

Slowlog thresholds for all indices

Add slowlog thresholds for all indices

PUT /_all/_settings 
{
"index.search.slowlog.threshold.query.warn": "10s",
"index.search.slowlog.threshold.query.info": "5s",
"index.search.slowlog.threshold.query.debug": "2s",

Requirements

maim
xclip

Set-up

Set this on your i3 config file ~/.i3/config

# Screenshots

	<?php declare(strict_types=1);

	if ($argc !== 3) {
	die("Usage: php optimise.php input.jpeg output.jpeg" . PHP_EOL);
	}

	$infile = $argv[1];
	$outfile = $argv[2];

	$img = imageCreateFromJPEG($infile);

	<?php

	namespace Tests\Concerns;

	use App\Models\User;
	use Tymon\JWTAuth\Facades\JWTAuth;

	trait AttachJwtToken
	{
	/**

	WITH RECURSIVE fibonacci(recursion_level, fibonacci_number, next_number)
	AS (
	# Base Case
	SELECT 0 AS recursion_level,
	0 AS fibonacci_number,
	1 AS next_number
	UNION ALL
	# Recursion query
	SELECT recursion_level + 1 AS recursion_level,
	next_number AS fibonacci_number,

	export function flatMap<T, U>(array: T[], callbackfn: (value: T, index: number, array: T[]) => U[]): U[] {
	return Array.prototype.concat(...array.map(callbackfn));
	}