slowprog

Update: I'm using this strategy, at the moment: https://github.com/jamiejackson/docker-secret-hash

This is a helper script for updating a secret in a running service. It does cause the service containers to restart (there's no avoiding that), but it does so as elegantly/conveniently as I know how.

See the motivation for this script, as well as alternatives, here.

Caveat:

Secret names with a length approaching 64 characters might exhibit weird behavior, as this relies on a version token being tacked onto the secret name. Since the secret name is truncated to 64 characters, a long name might result in a smaller (or nonexistent) version token, leading to uniqueness problems and unexpected behavior.

Use xdebug with docker on macOS and PhpStorm

To use xdebug with macOS and docker is quite, let´s call it tricky ;)

The following steps need to be proceed to get it working:

use the config from the xdebug.ini wihtin your docker web container. Important: set remote_connect_back to off

UPDATE

Install tmux

brew install tmux

Start tmux (https://gitlab.com/gnachman/iterm2/wikis/TmuxIntegration)

Run tmux -CC or tmux -CC attach in iTerm2 and then menu is shown on terminal:

ESC to detach
C to run commands
X to force quit
L for log

Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.

This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.

There is a companion feature matrix of various tools. Comments are welcome in the same manner.

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

	deploy:live:
	image: 1drop/docker:git
	stage: deploy
	when: manual
	environment:
	name: production
	url: https://www.somecustomer.de
	before_script:
	- eval $(ssh-agent -s)
	- ssh-add <(echo "$SSH_PRIVATE_KEY")

	def json_error(status_code: int, exception: Exception) -> web.Response:
	"""
	Returns a Response from an exception.
	Used for error middleware.
	:param status_code:
	:param exception:
	:return:
	"""
	return web.Response(
	status=status_code,

	ssh-keygen -t rsa -b 4096 -m PEM -f jwtRS256.key
	# Don't add passphrase
	openssl rsa -in jwtRS256.key -pubout -outform PEM -out jwtRS256.key.pub
	cat jwtRS256.key
	cat jwtRS256.key.pub

	/**
	* Merge defaults with user options
	* @private
	* @param {Object} defaults Default settings
	* @param {Object} options User options
	* @returns {Object} Merged values of defaults and options
	*/
	var extend = function ( defaults, options ) {
	var extended = {};
	var prop;