| # 1. update your aws cli | |
| # https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html | |
| # | |
| # 2. update your existing cluster with capacity providers support | |
| CLUSTER_NAME=fargate | |
| SERVICE_NAME=myservice | |
| FARGATE_WEIGHT=1 | |
| FARGATE_SPOT_WEIGHT=1 | |
| FARGATE_BASE=1 | |
| FARGATE_SPOT_BASE=0 |
Custom format for displaying bytes as kb, mb, gb or tb.
Response to a few places on the internet: https://productforums.google.com/forum/#!topic/docs/x_T_N-yRUYg And here: https://stackoverflow.com/questions/1533811/how-can-i-format-bytes-a-cell-in-excel-as-kb-mb-gb-etc
Here is one that I have been using:
[<1000000]0.00," KB";[<1000000000]0.00,," MB";0.00,,," GB"
| ### KERNEL TUNING ### | |
| # Increase size of file handles and inode cache | |
| fs.file-max = 2097152 | |
| # Do less swapping | |
| vm.swappiness = 10 | |
| vm.dirty_ratio = 60 | |
| vm.dirty_background_ratio = 2 |
This is a quick guide to install PostgreSQL 10 - tested on Ubuntu 16.04 but likely can be used for Ubuntu 14.04 and 17.04 as well, with one minor modification detailed below.
To make life simple, remove all other versions of Postgres. Obviously not required, but again, makes life simple. If you have data in your previous version of postgres that you'd like to retain, then this is not recommended. Instead, you'll have to use pg_upgrade or pg_upgradecluster.
| const fs = require('fs'); | |
| const Converter = require('./converter.js'); | |
| const options = { | |
| name: process.argv[3], | |
| description: process.argv[4], | |
| activate: process.argv[5], | |
| }; | |
| const converter = new Converter(JSON.parse(fs.readFileSync(process.argv[2])), options); |
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:
This script can help you find and remove unused AWS snapshots and volumes.
There is hardcoded list of regions that it searches, adjust the value to suit your needs.
Use snapshot.py snapshot-report to generate report.csv containing information about all snapshots.
snapshot.py snapshot-cleanup lets you interactively delete snapshot if it finds it is referencing unexisting resources.
./snapshots.py --help
This procedure explains how to install MySQL using Homebrew on macOS Sierra 10.12
$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"At this time of writing, Homebrew has MySQL version 5.7.15 as default formulae in its main repository :
| @register.inclusion_tag('admin/submit_line.html', takes_context=True) | |
| def submit_row(context): | |
| """ | |
| Displays the row of buttons for delete and save. | |
| """ | |
| ctx = original_submit_row(context) | |
| ctx.update({ | |
| 'show_save_and_add_another': context.get('show_save_and_add_another', ctx['show_save_and_add_another']), | |
| 'show_save_and_continue': context.get('show_save_and_continue', ctx['show_save_and_continue']), |