efrecon

namespace eval ::druct {
    namespace eval types {}
    namespace export {[a-z]*}
    namespace ensemble create
}

proc ::druct::new { type varname } {
    set typedef [Definition $type]
    if { ![info exists $typedef] } {
        return -code error "$type does not exist!"

efrecon

!/bin/sh

warn() {
  printf "%s\n" "$*" 1>&2
}

verbose() {
  if [ "$VERBOSE" = "1" ]; then printf "%s\n" "$*" 1>&2; fi
}

efrecon

#!/bin/bash

names=$(docker ps --format "{{.Names}}")
echo "tailing $names"

while read -r name
do
  # eval to show container name in jobs list
  eval "docker logs -f --tail=5 \"$name\" | sed -e \"s/^/[-- $name --] /\" &"
  # For Ubuntu 16.04

efrecon

git fetch
git branch -a
git diff remotes/origin/HEAD

efrecon

echo "SELECT table_schema || '.' || table_name FROM information_schema.tables WHERE table_type = 'BASE TABLE' AND table_schema NOT IN ('pg_catalog', 'information_schema');" | psql -U postgres -d dbname -q -t

efrecon

psql -U postgres -l -t

efrecon

#!/bin/sh

# Check if the URL passed as a first argument maches some of the HTTP codes that
# are passed in the following arguments as regular expressions.  The list of
# error codes can be omitted, in which case this will be the whole "OK" range,
# from 200 to 299.  When the remote site answers one of the matching code an
# exit code of 0 is returned, otherwise an error is returned.
#
# Additional options can be passed:
# -v to increase verbosity.

efrecon

#!/bin/sh

usage() {
  if [ -n "$1" ]; then echo $1 1>&2; fi
  cat << USAGE >&2
Usage:
  $0 options.. [--] files...
  -v | --verbose                  Be more verbose when waiting
  --no-header                     Do not consider CSV file with header
  --dry-run                       Do not modify files in place, show result instead

efrecon

#! /usr/bin/env bash

VERBOSE=0
GHUSER=efrecon
SNAPSHOT=0
while [ $# -gt 0 ]
do
  case "$1" in
    -u | --user)
        GHUSER=$2

efrecon

UNIX-Style postgreSQL Initialisation

Introduction

This script aims at easily initialising access rights for users in postgreSQL databases in a UNIX:y way. The script will read a configuration file where fields are separated by the colon (:) sign (e.g. analogical to /etc/password). The file is able to express and map rwx-style permissions onto GRANT-style privileges with the database and its schema/tables, thus simplifying initialisation of the authorisations, but also use of users created