dknecht

You can actually use CloudFlare and stay on Github pages. In the CloudFlare DNS editor you can point your root at github's cname address and everything will work. If you choose not to enable CloudFlare proxy service you can still use the DNS to flatten Github's cname. See http://blog.cloudflare.com/introducing-cname-flattening-rfc-...

I am from CloudFlare. If you need help getting setup feel free to email me (dane AT cloudflare.com).

Sorry. I wrote this after a long day and replied above that this should read per minute and not per second.

EDIT: Sorry wrote this after a long day. That should read per minute and not per second.

For most customer they are stored just long enough to provide support, create aggregates for the analytics dashboard, and update threat profiles. Our enterprise customers have the option collect raw logs through SFTP for up to 3 days.

CloudFlare generates 50gb/s of logs globally and have handled collecting this volume in two ways. Historically the logs are sent to a local syslog-ng through the use of a PIPE and the forwarded to central logger. This can be done with nginx with no patches by just treating the PIPE as file. Just make sure you do a little buffering inside nginx.

access_log /dev/nginx_access log_format_name buffer=64k flush=10s;

Since this is a pipe there is still some blocking IO, but no worse off then writing to local file.

The way we are migrating will be non-blocking IO through the use of Lua Resty log module ( https://github.com/cloudflare/lua-resty-logger-socket ).

We will write up a blog post at some point but hopefully this is useful to you. In the future we are going to be going one step further and have NGINX emit protobuff files. Feel free to email dane AT cloudflare.com if you have any questions.

We use a supervising process [1] that has bound the sockets and the pass in the file descriptors to Go process. When the new process is ready to take connections it sense a signal to the original process to shut down.

[1] https://github.com/cloudflare/circus/commits/cloudflare2

Every request that passes through CloudFlare goes through Lua. It has how we look up and apply a customer rules to a recess. We just recently realized a non-blocking logger option for Nginx [2] using Lua and are in the process of developing a new KT library [3] in Lua.

Here are the most recent lua libraries we have open sourced... [1] https://github.com/agentzh/lua-resty-lock [2] http://github.com/cloudflare/lua-resty-logger-socket [3] http://github.com/cloudflare/lua-resty-kyototycoon

The Authy app is great and supports Google, Dropbox, CloudFlare, Amazon…

Yes. CloudFlare has it set that way with Network Solutions.

We originally considered building of off Unbound. It is great product and plan on switching our internal recursors from PDNS Recursor to Unbound in the future. The decision to build our own was because we are heavy user of Nginx and really like the concept of being able to easily create new modules that can be inserted at different points in DNS response pipeline. We will be blogging a lot more about the technical aspects of RRDNS in the future.

In addition the reason to host this on single domain vs your own site is that the users only have to download the resource once it once for all the sites they visit.

This is just the first of many projects CloudFlare has in the works being built with Go and is looking for more developers interested in Go.

This is metric that is commonly used in the popular webpagetest.org performances test

We would love to help, and have offered.

A link to screenshot https://skitch.com/dknecht/f9dad/amazon.com-online-shopping-...

They fixed it a few hours ago. My account is still showing I purchased a 100.