kumaraish

DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )

Is a useful one-liner which will give you the full directory name of the script no matter where it is being called from

These will work as long as the last component of the path used to find the script is not a symlink (directory links are OK). If you want to also resolve any links to the script itself, you need a multi-line solution:

SOURCE="${BASH_SOURCE[0]}"
while [ -h "$SOURCE" ]; do # resolve $SOURCE until the file is no longer a symlink

kumaraish

Intro

TCL-Expect scripts are an amazingly easy way to script out laborious tasks in the shell when you need to be interactive with the console. Think of them as a "macro" or way to programmaticly step through a process you would run by hand. They are similar to shell scripts but utilize the .tcl extension and a different #! call.

Setup Your Script

The first step, similar to writing a bash script, is to tell the script what it's executing under. For expect we use the following:

#!/usr/bin/expect

kumaraish

References:
	1. http://jekyllrb.com/docs/home/
	2. https://labs.sverrirs.com/jekyll/
	3. https://davidburela.wordpress.com/2015/11/28/easily-install-jekyll-on-windows-with-3-command-prompt-entries-and-chocolatey/
	4. http://guides.rubygems.org/ssl-certificate-update/#installing-using-update-packages

Jekyll v3.x requires Ruby version >= 2.0.0.

Ruby installation
	-installation via chocolatey

kumaraish

docker run 
  --user 0:0 
  --env MY_USR=$(id -u) 
  --env MY_GID=$(id -g)
  <my_image>
  bash -c 'zypper install -l -y xyz;
           echo "dummy:x:$MY_USR:$MY_GID:eusers:$PWD:/bin/bash" >> /etc/passwd;                 
           su - dummy -c "<command-to-be-run-with-host-users-permissions>"'

kumaraish

Client-side SSL

For excessively paranoid client authentication.

---

Updated Apr 5 2019:

because this is a gist from 2011 that people stumble into and maybe you should AES instead of 3DES in the year of our lord 2019.

some other notes: