git clone https://gist.github.com/dd6f95398c1bdc9f1038.git vault
cd vault
docker-compose up -d
export VAULT_ADDR=http://192.168.99.100:8200
Initializing a vault:
vault init
I've been fighting the same problem and have to say the hint provided here about resetting the launch services, and letting `launchd` do this at login (via Lingon) is invaluable. Thanks a lot for that, it makes FileVault far more usable! | |
After using this for a while, I have however discovered a side effect of resetting the launch services that is rather annoying--but I have also found a solution for it. | |
The _problem_ is that after resetting the launch services, calling a protocol handler registered by a user installed application is considered a **first time call** again, meaning it needs to be confirmed by the user (unless the app has been started directly before the call). Examples I stumbled upon are: | |
* bookmarking through the Pukka bookmarklet | |
* opening an Evernote note from a Spotlight search | |
* calling a `man` page in Safari through Bwana. |
# | |
# Tasks to keep your repository in sync with your Chef Server | |
# | |
# Author:: Matthew Kent (<[email protected]>) | |
# Copyright:: Copyright (c) 2010 Matthew Kent | |
# License:: Apache License, Version 2.0 | |
# | |
# Licensed under the Apache License, Version 2.0 (the "License"); | |
# you may not use this file except in compliance with the License. | |
# You may obtain a copy of the License at |
#!/usr/bin/env ruby | |
# | |
# One-liner | |
# curl -fsS https://gist.github.com/raw/542746/install_rvm.rb | ruby -e '$script=STDIN.read;eval $script' | |
# | |
# This script installs to /usr/local only. It assumes theres an | |
# admin group on your system - either "wheel", "admin", or "staff" | |
# | |
# Sudo is used a few times during the initial install. But anyone | |
# in admin group can manage rvm (regardless of sudo privelidges) |
From 966471712184cfb3b067f2ae8dad9d8e2a896cae Mon Sep 17 00:00:00 2001 | |
From: Bearice Ren <[email protected]> | |
Date: Tue, 20 Sep 2016 11:52:08 +0800 | |
Subject: [PATCH] add filter-aaaa option | |
--- | |
src/dnsmasq.h | 3 ++- | |
src/option.c | 3 +++ | |
src/rfc1035.c | 9 +++++++++ | |
3 files changed, 14 insertions(+), 1 deletion(-) |
/var/lib/docker/containers/*/*-json.log { | |
dateext | |
daily | |
rotate 365 | |
compress | |
delaycompress | |
missingok | |
} |
git clone https://gist.github.com/dd6f95398c1bdc9f1038.git vault
cd vault
docker-compose up -d
export VAULT_ADDR=http://192.168.99.100:8200
Initializing a vault:
vault init
odyssey-2016
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
# generated by Slic3r 1.37.2-prusa3d on Thu Dec 7 09:48:20 2017 | |
# Figured out by trial and error engineer metacollin | |
# Released as public domain. | |
# USE GLUESTICK FOR PRINT BED ADHESION | |
avoid_crossing_perimeters = 0 | |
bed_shape = 0x0,250x0,250x210,0x210 | |
bed_temperature = 110 | |
before_layer_gcode = ;BEFORE_LAYER_CHANGE\n;[layer_z]\n\n | |
bottom_solid_layers = 8 | |
bridge_acceleration = 1000 |
#!/bin/bash | |
# References | |
# https://devopsideas.com/benchmarking-disk-iops-aws-vs-digitalocean/ | |
# https://wiki.mikejung.biz/Benchmarking#Fio_Test_Options_and_Examples | |
# https://tobert.github.io/post/2014-04-17-fio-output-explained.html | |
# Requires linux packages: fio ioping |