Author: Peter Benjamin
Date: 01/15/2016
Revised: 01/20/2016
Purpose: Instructions for setting up/configuring citrix netscaler as it pertains to Echo-Cloud.
#!/usr/bin/env node | |
'use strict'; | |
/** | |
* Require dependencies | |
* | |
*/ | |
const program = require('commander'), | |
chalk = require("chalk"), | |
exec = require('child_process').exec, | |
pkg = require('./package.json'); |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".
#!/bin/bash -ex | |
# env > $HOME/cronenv | |
env -i $(cat $HOME/cronenv) "$@" |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )
Is a useful one-liner which will give you the full directory name of the script no matter where it is being called from
These will work as long as the last component of the path used to find the script is not a symlink (directory links are OK). If you want to also resolve any links to the script itself, you need a multi-line solution:
SOURCE="${BASH_SOURCE[0]}"
while [ -h "$SOURCE" ]; do # resolve $SOURCE until the file is no longer a symlink
FROM golang:1.9 AS build | |
LABEL maintainer "Peter Benjamin" | |
WORKDIR /go/src/github.com/petermbenjamin/go-hello-world | |
COPY . . | |
RUN go get -u -v github.com/golang/dep/cmd/dep \ | |
&& dep init \ | |
&& CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o hello-world . | |
FROM alpine | |
COPY --from=build /go/src/github.com/petermbenjamin/go-hello-world/hello-world /usr/bin/hello-world |
Create a template service file at /etc/systemd/system/[email protected]
. The template parameter will correspond to the name
of target host:
[Unit]
Description=Setup a secure tunnel to %I
After=network.target
/* | |
* I add this to html files generated with pandoc. | |
*/ | |
html { | |
font-size: 100%; | |
overflow-y: scroll; | |
-webkit-text-size-adjust: 100%; | |
-ms-text-size-adjust: 100%; | |
} |
octant master ↓·4 ✚1 …5 $ OCTANT_LISTENER_ADDR=0.0.0.0:8900 octant -vvv | |
2019-08-16T06:05:57.259Z DEBUG dash/dash.go:68 Loading configuration: /home/ubuntu/.kube/kind-config-kind | |
2019-08-16T06:05:57.262Z DEBUG cluster/cluster.go:269 initializing REST client configuration {"client-qps": 200, "client-burst": 400} | |
2019-08-16T06:05:57.263Z DEBUG cluster/cluster.go:104 created temp directory {"component": "cluster client", "dir": "/tmp/octant626661369"} | |
2019-08-16T06:05:57.263Z DEBUG dash/dash.go:95 initial namespace for dashboard is default | |
2019-08-16T06:05:57.267Z DEBUG describer/path_matcher.go:44 register path {"name": "overview", "path": "/"} | |
2019-08-16T06:05:57.267Z DEBUG describer/path_matcher.go:44 register path {"name": "overview", "path": "/workloads"} | |
2019-08-16T06:05:57.267Z DEBUG describer/path_matcher.go:44 register path {"name": "overview", "path": "/workloads/cron-jobs"} | |
2019-08-16T06:05:57.267Z DEBUG describe |