jeffhorton

user nginx;
# Set this to match the number of CPU cores
worker_processes 2;
events { worker_connections 1024; }
http {
    server_names_hash_bucket_size 64;
    types_hash_max_size 2048;
    server_tokens off;
    include mime.types;
    default_type application/octet-stream;

jeffhorton

javascript:(function(){window.rl = window.rl || []; function rlfunc() { $('span.message_sender, a.member').each(function (i, j) { for (var i = 0; i < window.rl.length; i++) { var re = new RegExp(rl[i], "ig"); if (j.className.match(re) || j.textContent.match(re)) { j.closest('ts-message').remove(); console.log('removing', re); } else { console.log('no match', re, j.className); } } } ) } var u = prompt('user partial'); if (u != null) { window.rl.push(u); console.log(window.rl); rlfunc() }; $('body').remove('DOMSubtreeModified', rlfunc()); $('body').on('DOMSubtreeModified', rlfunc());})();

jeffhorton

in hn comments related to this https://blog.sentry.io/2017/03/01/dodging-s3-downtime-with-nginx-and-haproxy.html

Heads up a simple yet production ready NGINX location block to proxy to a public s3 bucket looks like:
    # matches /s3/*
    location ~* /s3/(.+)$ {
        set $s3_host 's3-us-west-2.amazonaws.com';
        set $s3_bucket 'somebucketname'

        proxy_http_version 1.1;
        proxy_ssl_verify on;