start new:
tmux
start new with session name:
tmux new -s myname
# The same algorithm which is used in Google Analytics (https://support.google.com/analytics/answer/2731565?hl=en): | |
# Time-based expiry (including end of day): | |
# - After 30 minutes of inactivity | |
# - At midnight | |
# Enable dynamic scripting for Groovy (https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-scripting.html#_enabling_dynamic_scripting) | |
# ! WARNING: please read about security first | |
# Usage: | |
# |
# Maintainer: Jakub Hajek, [email protected] | |
# | |
# docker stack deploy -c stack-elastic.yml elastic | |
# | |
# The stack creates Elasticsearch cluster consiting of | |
# - 3 dedicated master nodes in order to keep quorum | |
# - 4 dedicated data nodes to manage CRUD, | |
# | |
# Docker compose file to easily deploy Elasticsearch cluster 7.x on Docker Swarm cluster. |
If you work on feature branches, like we do, that are based off a parent branch (e.g. the master branch of the main repository), you want to avoid your branch getting out of sync with the latest work in the parent branch.
As time goes by, your forked branch where you’re working can become significantly out of sync with the latest master branch. This may mean that merging your work
git clone https://github.com/denysdovhan/spaceship-prompt.git "$ZSH_CUSTOM/themes/spaceship-prompt"
ln -s "$ZSH_CUSTOM/themes/spaceship-prompt/spaceship.zsh-theme" "$ZSH_CUSTOM/themes/spaceship.zsh-theme"
#!/bin/bash | |
#Author Hai Dam <[email protected]> | |
export DOCKER_COMPOSE_VERSION="1.24.0" | |
set -eu | |
function echocolor { | |
echo "$(tput setaf 2) $1 $(tput sgr0)" | |
} |
#!/bin/sh | |
if [ -z "$1" ] ; then userid=$(whoami); else userid=$1; fi | |
sudo tee /etc/sudoers.d/${userid} > /dev/null <<EOF | |
${userid} ALL=(root) NOPASSWD:ALL | |
EOF |
(still a work-in-progress)