Skip to content

Instantly share code, notes, and snippets.

#!/bin/bash
# 0 * * * * /Users/imiell/git/work/bin/home/slack_start_stop.sh start
# 3-59 * * * * /Users/imiell/git/work/bin/home/slack_start_stop.sh stop
DO_START=0
DO_STOP=0
while [ "$1" != "" ]; do
case $1 in
@pirate
pirate / docker-compose-backup.sh
Last active October 25, 2024 01:51
Backup a docker-compose project, including all images, named and unnamed volumes, container filesystems, config, logs, and databases.
#!/usr/bin/env bash
### Bash Environment Setup
# http://redsymbol.net/articles/unofficial-bash-strict-mode/
# https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html
# set -o xtrace
set -o errexit
set -o errtrace
set -o nounset
set -o pipefail
@lemiorhan
lemiorhan / ReleaseViaJGitFlow.md
Last active September 3, 2024 20:35
How to make a release with Git and Maven via JGitFlow

How to make a release with Git and Maven via JGitFlow

Imagine that you are versioning your sourcecode in git and building your code via maven. You need to make releases before deploying to production regularly. What should be the strategy we need to follow for releasing?

I've used maven-release-plugin for years to make releases. It worked perfectly with maven and svn, but we started to face problems when we migrated our code to git and to make releases on git.

After checking the literature, we decided to use JGit-Flow which is a maven plugin based on and is a replacement for the maven-release-plugin enabling support for git-flow style releases via maven.

I do not want to explain the details much because there are many great posts explaining all.