<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>localhost.pbcopy</string>
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Files | |
data.location=/home/threebean/.task | |
#include /home/threebean/.task/solarized-dark-256.theme | |
_forcecolor=yes | |
defaultwidth=160 | |
include /usr/local/share/doc/task/rc/dark-violets-256.theme | |
report.work_report.description=now |
I have spent quite a bit of time figuring out automounts of NFS shares in OS X...
Somewhere along the line, Apple decided allowing mounts directly into /Volumes should not be possible:
/etc/auto_master (see last line):
#
# Automounter master map
#
+auto_master # Use directory service
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
set-option -g default-terminal "xterm-256color" | |
set-window-option -g xterm-keys on | |
run-shell "tmux setenv -g TMUX_VERSION $(tmux -V | cut -c 6-)" | |
setw -g mode-keys vi | |
unbind C-b | |
# remap prefix to Control + Space |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DASEL_VER="1.15.0" | |
CRI_VER="1.5.1" | |
# | |
# install dasel | |
# | |
curl -fsSL "https://github.com/TomWright/dasel/releases/download/v${DASEL_VER}/dasel_linux_amd64" -o /usr/local/bin/dasel | |
chmod +x /usr/local/bin/dasel |
WARNING: This hasn't been tested extensively outside of my environment. Your mileage may vary.
Assumptions:
- Any security group modifications or creation that CAPA does that's not specifically flagged below are acceptable for a brief disruption when modified
- This is valid as of CAPA 2.0.2. This may not work with new versions (e.g., the steps were different pre-2.x and it was easier to import even the VPC itself pre-2.x)
Importing CAPA Cluster (using BYO VPC):
- Make sure
AWSManagedControlPlane.spec.eksClusterName
matches the EKS cluster name - Optionally set
AWSManagedControlPlane.spec.network.securityGroupOverrides.controlplane
to match the security group you have on the EKS controlplane. If you have extra security groups I haven't been able to figure out how to import those into CAPA but they stay attached to the EKS cluster and are just ignored by CAPA - Set the VPC information according to the BYO VPC specs https://cluster-api-aws.sigs.k8s.io/topics/bring-your-own-aws-infrastructure.html#configur
OlderNewer