biiont

# Prepare
mkdir -p "${HOME}/path without/symlinks"; ln -s "${HOME}/path without" "${HOME}/path with"
 
TESTPATH="${HOME}/..///${USER}/path with/symlinks///"; echo "${TESTPATH}"
 
echo "Absolute path: '$(realpath -m ${TESTPATH})'"
echo "Canonical path: '$(realpath -s -m ${TESTPATH})'"
echo "Relative to '/usr/bin': '$(realpath -s -m --relative-to="/usr/bin" ${TESTPATH})'"
echo "Canonical relative to '/usr/bin': '$(realpath -m --relative-to="/usr/bin" ${TESTPATH})'"
echo "Relative with base '/usr/bin': '$(realpath -s -m --relative-base="/usr/bin" ${TESTPATH})'"

aaronjensen

#!/usr/bin/env ruby
Dir.chdir File.join(__FILE__, "../..")

unless ENV['EDITOR']
  puts "No EDITOR found. Try:"
  puts "export EDITOR=vim"
  exit 1
end

unless ARGV.count == 2

fnichol

Format Changes to Test Kitchen's kitchen.yml File

This is happening thanks to a refactoring of the data manipulation code formerly in Kitchen::Config.

There are now 3 main configuration blocks that can be placed in the various levels:

• driver: Configurtation relavent to Kitchen drivers. This is a combination of what was driver_plugin and driver_config. Backwards compatability is guarenteed with the legacy formats for a time, then will be deprecated (with a warning when encountered), then will be removed in a future release.
• provisioner: Configuration relating to the automation tool being used. Currently supporting "chef_solo" and "chef_zero". Previously several Chef-related config paths were dumped in a Suite block, namely data_path, data_bags_path, environments_path, nodes_path, roles_path, etc. These will be supported for backwards compatability, then will be deprecated (with a warning when encountered), then will be removed in a future release.
• busser: Configuration rela

leedm777

#!/bin/sh

#
# Forwards SSH agent into a Docker container running in the active
# docker-machine
#

PROGNAME=$(basename $0)

NAME=$(docker-machine active)

tegansnyder

sudo dscacheutil -flushcache;sudo killall -HUP mDNSResponder;say flushed 

fnichol

SUITE_NAME=default

# create a bats subdirectory under your desired suite
mkdir -p test/integration/$SUITE_NAME/bats

# create an initial "canary" bats test file
# more examples at:
# * https://github.com/fnichol/chef-rvm/tree/master/test/integration/rubies/bats
# * https://github.com/fnichol/chef-ruby_build/tree/master/test/integration/alltherubies/bats
# * https://github.com/sstephenson/bats

peplin

# Source accepts the protocol s3:// with the host as the bucket
# access_key_id and secret_access_key are just that
s3_file "/var/bulk/the_file.tar.gz" do
  source "s3://your.bucket/the_file.tar.gz"
  access_key_id your_key
  secret_access_key your_secret
  owner "root"
  group "root"
  mode 0644
end

bossjones

#!/usr/bin/execlineb -P
# NOTE: cont-init.d/30-init-dbus
# -*- mode: bash -*-
# vi: set ft=bash:


with-contenv

trap -x
{

anthonysterling

# Usage:    IE={box} vagrant up
#
# Eg.       IE=XPIE6 vagrant up

boxes = {
    "XPIE6"     => "http://aka.ms/vagrant-xp-ie6",
    "XPIE8"     => "http://aka.ms/vagrant-xp-ie8",
    "VistaIE7"  => "http://aka.ms/vagrant-vista-ie7",
    "Win7IE8"   => "http://aka.ms/vagrant-win7-ie8",
    "Win7IE9"   => "http://aka.ms/vagrant-win7-ie9",

trinitronx

                    GNU GENERAL PUBLIC LICENSE
                       Version 3, 29 June 2007

 Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

                            Preamble

  The GNU General Public License is a free, copyleft license for