.env file for me sparing me the need to pollute my session with environment variables.
I've been using Fish shell for years which is great and all, but one thing that has got me frustrated is using it with .env files.
When attempting to run source .env in a project, I usually encounter this problem:
| bind f "use weapon_flashbang" | |
| bind c "use weapon_smokegrenade" | |
| bind g "use weapon_hegrenade" | |
| bind x "use weapon_incgrenade;use weapon_molotov" | |
| bind "kp_ins" "buy vesthelm;" | |
| bind "kp_del" "buy ak47; buy m4a1;" | |
| bind "kp_enter" "buy flashbang;" | |
| bind "kp_plus" "buy smokegrenade;" | |
| bind "kp_minus" "buy sg556; buy aug;" |
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.)
