| window: | |
| # Window dimensions (changes require restart) | |
| # | |
| # Number of lines/columns (not pixels) in the terminal. The number of columns | |
| # must be at least `2`, while using a value of `0` for columns and lines will | |
| # fall back to the window manager's recommended size. | |
| dimensions: | |
| columns: 500 | |
| lines: 30 |
a gist to recap the current status, also available as library picker!
do one thing only and do it well
| #=======================================================================# | |
| # extract_data.py # | |
| #=======================================================================# | |
| # usage: extract_data.py [-h] [-i INPUT_DIR] [-o OUTPUT_DIR] | |
| # | |
| # This program extracts provision numbers from a set of documents. | |
| # | |
| # optional arguments: | |
| # -h, --help show this help message and exit | |
| # -i INPUT_DIR, --input_dir INPUT_DIR |
Let's look at an example of how to launch a Kubernetes cluster from scratch on DigitalOcean, including kubeadm, an Nginx Ingress controller, and Letsencrypt certificates.
We'll be creating a four-node cluster (k8s-master, k8s-000...k8s-002), load balancer, and ssl certificates.
A curated list of AWS resources to prepare for the AWS Certifications
A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.
A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.
With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.
We use GraphQL to dyn
| #!/bin/bash | |
| sudo mount -o remount,size=10G,noatime /tmp | |
| echo "Done. Please use 'df -h' to make sure folder size is increased." |
Short version: I strongly do not recommend using any of these providers. You are, of course, free to use whatever you like. My TL;DR advice: Roll your own and use Algo or Streisand. For messaging & voice, use Signal. For increased anonymity, use Tor for desktop (though recognize that doing so may actually put you at greater risk), and Onion Browser for mobile.
This mini-rant came on the heels of an interesting twitter discussion: https://twitter.com/kennwhite/status/591074055018582016
This is a simple way to backup your MySQL tables to Amazon S3 for a nightly backup - this is all to be done on your server :-)
Sister Document - Restore MySQL from Amazon S3 - read that next
this is for Centos 5.6, see http://s3tools.org/repositories for other systems like ubuntu etc
