Julián Gutiérrez juliangut

wrk -t4 -c400 -d10s http://127.0.0.1:1337/

PHP

Running 10s test @ http://127.0.0.1:1337/
  4 threads and 400 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
 Latency 7.02ms 6.94ms 82.86ms 85.27%

I recently switched over to neovim (see my screenshots at the bottom). Below is my updated config file.

It's currently synchronized with my .vimrc config except for a block of neovim-specific terminal key mappings.

This is still a work in progress (everyone's own config is always a labor of love), but I'm already extremely pleased with how well this is working for me with neovim. While terminal mode isn't enough to make me stop using tmux, it is quite good and I like having it since it simplifies my documentation workflow for yanking terminal output to paste in a markdown buffer.

These days I primarily develop in Go. I'm super thrilled and grateful for fatih/vim-go,

Think twice before abandoning Xorg. Wayland breaks everything!

Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.

Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.

The Wayland project seems to operate like they were starting a greenfield project, whereas at the same time they try to position Wayland as "the X11 successor", which would clearly require a lot of thought about not breaking, or at least providing a smooth upgrade path for, existing software.

In fact, it is merely an incompatible alternative, and not e

	##
	## This nginx.conf servers as the main config file for webflow reverse proxy
	##
	## RCS:
	## https://gist.github.com/sansmischevia/5617402
	##
	## Hardening tips:
	## http://www.cyberciti.biz/tips/linux-unix-bsd-nginx-webserver-security.html
	##

	events {
	worker_connections 1024;
	}

	http {
	default_type text/html;
	access_log /dev/stdout;
	sendfile on;
	keepalive_timeout 65;

	input {

	file {
	type => "php-error"
	path => "/var/www/error_log"
	sincedb_path => "/opt/logstash/sincedb-access"
	}

	}

	/vendor/*
	/composer.lock

	# ignore certain files
	*.pyc
	*.swp
	*.dmg
	*.gz
	*.iso
	*.jar

	server {
	listen 80;
	server_name *.foo.example.com;

	# We need this to resolve the host, because it's a wildcard.
	# This is google's DNS server.
	resolver 8.8.8.8;

	include /etc/nginx/includes/proxy.conf;

	openssl rsa -in ~/.ssh/id_rsa -outform pem > id_rsa.pem
	chmod 600 id_rsa.pem

	#
	# Configure php error log filtering
	#
	filter {
	if [type] == "php-error" {
	multiline {
	pattern => "%{SYSLOG5424SD:timestamp} PHP (?:%{LOGLEVEL:loglevel})"
	negate => true
	what => "previous"
	}