All of the following information is based on go version go1.17.1 darwin/amd64
.
GOOS | Out of the Box |
---|---|
aix |
✅ |
android |
✅ |
# Stick this in your home directory and point your Global Git config at it by running: | |
# | |
# $ git config --global core.attributesfile ~/.gitattributes | |
# | |
# See https://tekin.co.uk/2020/10/better-git-diff-output-for-ruby-python-elixir-and-more for more details | |
*.c diff=cpp | |
*.h diff=cpp | |
*.c++ diff=cpp | |
*.h++ diff=cpp |
This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.
I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/
in my Dockerfiles, and also work from
isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/
.
At the end of the day, vendoring (and committing vendor/
) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:
-- Table information like sortkeys, unsorted percentage | |
-- see http://docs.aws.amazon.com/redshift/latest/dg/r_SVV_TABLE_INFO.html | |
SELECT * FROM svv_table_info; | |
-- Table sizes in GB | |
SELECT t.name, COUNT(tbl) / 1000.0 AS gb | |
FROM ( | |
SELECT DISTINCT datname, id, name | |
FROM stv_tbl_perm | |
JOIN pg_database ON pg_database.oid = db_id |
#! /usr/bin/env ruby | |
require 'rack' | |
require 'sidekiq' | |
require 'sidekiq/web' | |
require 'sidekiq-failures' | |
url = ARGV[0] || 'redis://localhost:6379' | |
Sidekiq.configure_client do |config| | |
config.redis = { size: 1, url: url } |
require 'sidekiq/api' | |
if File.basename($0) == 'sidekiq' | |
Thread.new do | |
loop do | |
begin | |
t0 = Time.now | |
qcount = 0 | |
njobs = 0 |
=begin | |
This script uses the AWS v2 API | |
Gemfile: | |
source "https://rubygems.org" | |
gem "aws-sdk", "2.0.17.pre" |
#!/bin/bash | |
SOURCEINSTANCE=${SOURCEINSTANCE:-''} | |
SOURCEUSER=${SOURCEUSER:-'admin'} | |
SOURCEPORT=${SOURCEPORT:-'5439'} | |
SOURCEDB=${SOURCEDB:-'db'} | |
SOURCESCHEMA=${SOURCESCHEMA:-'public'} | |
SCHEMA=${SCHEMA:-'public'} | |
echo "CREATE TABLE ${SCHEMA}.${TABLE} (" | |
psql -h ${SOURCEINSTANCE} -U ${SOURCEUSER} -p ${SOURCEPORT} ${SOURCEDB} -t -c "select (\"column\" || ' ' || type || ' ENCODE ' || encoding || ',' ) from pg_table_def where schemaname='$SCHEMA' and tablename = '$TABLE'" | sed 's/ENCODE none/ENCODE RAW/' | sed '$d' | sed '$ s/,$//' | |
echo ")" |
Note: This was written using elasticsearch 0.9.
Elasticsearch will automatically create an index (with basic settings and mappings) for you if you post a first document:
$ curl -X POST 'http://localhost:9200/thegame/weapons/1' -d \
'{
"_id": 1,