- command line values (for example, -u my_user, these are not variables)
- role defaults (defined in role/defaults/main.yml)
- inventory file or script group vars
- inventory group_vars/all
# N.B. The only tool missing here that is mentioned in the document is `zenmap` | |
# purely because this image is intended to be run via a CLI and `zenmap` is a GUI | |
# to `nmap` i.e. one can play around with the tools by running: | |
# | |
# $ docker build --name bite_size_networking:latest . | |
# $ docker run --rm -d --name bsn_test bite_size_networking:latest | |
# $ docker exec -it bsn_test bash | |
# | |
# Alternatively, one can change the `ENTRYPOINT` to `["bash"]` and run: | |
# |
umask 022 | |
export PATH=~/bin:`echo $PATH | sed 's|:/bin:|&/opscode/chefdk/bin:/mnt/c/Users/Sean/AppData/Local/chefdk/gem/ruby/2.4.0/bin:/opscode/chefdk/embedded/bin:|'` |
################## | |
### config.yml ### | |
################## | |
version: 2 | |
jobs: | |
build: | |
docker: | |
- image: circleci/python:3.6 | |
steps: |
I work as a full-stack developer at work. We are a Windows & Azure shop, so we are using Windows as our development platform, hence this customization.
For my console needs, I am using Cmder which is based on ConEmu with PowerShell as my shell of choice.
Yes, yes, I know nowadays you can use the Linux subsystem on Windows 10 which allow you to run Ubuntu on Windows. If you are looking for customization of the Ubuntu bash shell, check out this article by Scott Hanselman.
resource_name :email_alias | |
property :address | |
property :recipients, Array | |
default_action :create | |
action :create do | |
with_run_context :root do |
This has been moved into the official Chef docs:
https://docs.chef.io/custom_resources_notes.html
This is by far the most recommended way of writing resources for all users. There are two gotchas which we're working through:
- For helper functions that you used to write in your provider code or used to mixin to your provider code, you have to use an
action_class do ... end
block.
# Installing ScyllaDB cluster in AWS with RAID0 array | |
# Prerequisites: | |
# - CentOS 7 (x86_64) with Updates HVM (available on AWS Marketplace) | |
# - Instance type with 2 hard drives for RAID0 array | |
SEED="10.0.0.11" | |
CLUSTER_NAME="Scylla Cluster" | |
PRIVATE_IP=$(curl -s http://169.254.169.254/latest/meta-data/local-ipv4) | |
######### Create RAID0 Array ############ |
For some reason, the network interfaces in ubuntu/wily64 fail to configure at boot. The interfaces are renamed during boot, with dmesg
reporting things like udev renamed network interface eth0 to enp1s0. This is apparently the result of a change in systemd. You can read about it here:
Starting with v197 systemd/udev will automatically assign predictable, stable network interface names for all local Ethernet, WLAN and WWAN interfaces. This is a departure from the traditional interface naming scheme ("eth0", "eth1", "wlan0", ...), but should fix real problems.
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
#!/bin/bash | |
set -e | |
#set -x | |
TOKEN=$( cat /root/.github-token ) | |
BASEURL="https://api.github.com/orgs/${1}/repos?type=owner&access_token=${TOKEN}&per_page=100" | |
BACKUPS_ZFS="zones/$( zonename )/data/backup/github" |