Recommended by Fabien Loudet, Senior SysOps at Rosetta Stone
The vipe program from the moreutils package allows to "insert a text editor into a pipe". That is, run your EDITOR in the middle of a unix pipeline and edit the data that is piped.
command1 | vipe | command2
| <?php | |
| //----------------------------------------------------------/ | |
| // responsive images [ 1) add img-responsive class 2) remove dimensions ] | |
| //----------------------------------------------------------/ | |
| function bootstrap_responsive_images( $html ){ | |
| $classes = 'img-responsive'; // separated by spaces, e.g. 'img image-link' | |
| // check if there are already classes assigned to the anchor | |
| if ( preg_match('/<img.*? class="/', $html) ) { |
| import ast | |
| import datetime | |
| import json | |
| import sys | |
| import requests | |
| import urllib | |
| from tabulate import tabulate | |
| url = "https://www.whatruns.com/api/v1/get_site_apps" | |
| data = {"data": {"hostname": sys.argv[1], "url": sys.argv[1], |
| /** | |
| * Hypertext Transfer Protocol (HTTP) response status codes. | |
| * | |
| * @see {@link https://en.wikipedia.org/wiki/List_of_HTTP_status_codes} | |
| */ | |
| export enum HttpStatusCode { | |
| /** | |
| * The server has received the request headers and the client should proceed to send the request body | |
| * (in the case of a request for which a body needs to be sent; for example, a POST request). |
This guide assumes that you recently run brew upgrade postgresql and discovered to your dismay that you accidentally bumped from one major version to another: say 9.3.x to 9.4.x. Yes, that is a major version bump in PG land.
First let's check something.
brew info postgresqlThe top of what gets printed as a result is the most important:
| # source : http://code.google.com/p/natvpn/source/browse/trunk/stun_server_list | |
| # A list of available STUN server. | |
| stun.l.google.com:19302 | |
| stun1.l.google.com:19302 | |
| stun2.l.google.com:19302 | |
| stun3.l.google.com:19302 | |
| stun4.l.google.com:19302 | |
| stun01.sipphone.com | |
| stun.ekiga.net |
| # Credit http://stackoverflow.com/a/2514279 | |
| for branch in `git branch -r | grep -v HEAD`;do echo -e `git show --format="%ci %cr" $branch | head -n 1` \\t$branch; done | sort -r |
This gist assumes you are migrating an existing site for www.example.com — ideally WordPress — to a new server — ideally Ubuntu Server 16.04 LTS — and wish to enable HTTP/2 (backwards compatibile with HTTP/1.1) with always-on HTTPS, caching, compression, and more. Although these instructions are geared towards WordPress, they should be trivially extensible to other PHP frameworks, other FastCGI backends, and even non-FastCGI backends (using proxy in lieu of fastcgi in the terminal Caddyfile stanza).
Quickstart: Use your own naked and canonical domain names instead of example.com and www.example.com and customize the Caddyfile and VCL provided in this gist to your preferences!
These instructions target Varnish Cache 4.1, PHP-FPM 7.0, and Caddy 0.10. (I'm using MariaDB 10.1 as well, but that's not relevant to this guide.)
