907 karma · joined July 27, 2015
> It's the entire reason there are 2 other branches of government.
You have DHS officials refusing to obey a court order[0] and the White House refusing to share information with Congress[1]. Where are the checks and balances?
0. https://www.theguardian.com/us-news/2017/jan/29/customs-bord...
1. http://thehill.com/homenews/senate/317006-rubio-state-asked-...
0. http://www.politico.com/story/2017/01/michael-flynn-muslim-b...
> using the exact list that President Obama signed into law
Yes, it's the same list of countries... with much, much broader restrictions placed upon them in this instance, to the point that some of the restrictions may violate the Immigration and Nationality Act of 1965 (point[0], counterpoint[1]).
0. https://www.nytimes.com/2017/01/27/opinion/trumps-immigratio...
1. http://www.nationalreview.com/article/444371/donald-trump-ex...
Caddy was maybe an odd choice but it performs well and it's been a breath of fresh air after dealing with some gnarly NGINX and Apache configurations in the past. So far it's been easy to maintain and there's a clear CDN migration path (Fastly). I'm using Docker's official PHP-FPM images[1] to serve multiple sites with some isolation, sharing Caddy, Varnish, and MariaDB instances.
I'm not sure if this solution has value for anyone else but I've been plugging it here and there in case there is!
0. https://gist.github.com/mwpastore/f42f6f1309a7b067519f4c08e1...
I found this[0] but it's prerelease and looks like it hasn't been touched in five years. Anyone know of any other solutions like this? Good idea? Bad idea?
I posted a gist[0] with my Caddy+Varnish+PHP-FPM configuration and a README explaining the hows and whys. I'm moving a bunch of WordPress sites from Apache/mod_php to this configuration (each site's PHP-FPM instance is Dockerized, but that's out of the scope of the gist). Hopefully someone finds it helpful!
0. https://gist.github.com/mwpastore/f42f6f1309a7b067519f4c08e1...
proxy / 127.0.0.1:8080 {
except /favicon.ico /robots.txt /assets /plainpages /staticstuff /test1
transparent
}
0. https://caddyserver.com/docs/proxyWhen I was getting started with a language last year I found a missing feature in a module of an open source library and submitted a very simple PR to add the feature. The maintainer asked me to completely refactor the module. I admittedly overreacted to this request—as I perceived it to be way too big of an ask—before settling down and getting to work on it. Then it literally took almost six months for the maintainer to review and merge my PR because of the intensity of the refactoring and performance regressions. (I would get some small piece of feedback, submit a fix or more information, wait weeks and weeks to hear back again, repeat ad naseum.)
So yes, issue-reporters and PR-submitters can be irritating, demanding, and disrespectful of maintainers' time, but maintainers can be just as bad.
Postscript: I don't regret the time I spent on it because it was an awesome learning experience, but it was certainly frustrating at the time!