(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
Alex en_US # Most people recognize me by my voice. | |
Alice it_IT # Salve, mi chiamo Alice e sono una voce italiana. | |
Alva sv_SE # Hej, jag heter Alva. Jag är en svensk röst. | |
Amelie fr_CA # Bonjour, je m’appelle Amelie. Je suis une voix canadienne. | |
Anna de_DE # Hallo, ich heiße Anna und ich bin eine deutsche Stimme. | |
Carmit he_IL # שלום. קוראים לי כרמית, ואני קול בשפה העברית. | |
Damayanti id_ID # Halo, nama saya Damayanti. Saya berbahasa Indonesia. | |
Daniel en_GB # Hello, my name is Daniel. I am a British-English voice. | |
Diego es_AR # Hola, me llamo Diego y soy una voz española. | |
Ellen nl_BE # Hallo, mijn naam is Ellen. Ik ben een Belgische stem. |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
function hangups (req, res, next){ | |
var reqd = domain.create() | |
reqd.add(req) | |
reqd.add(res) | |
reqd.on('error', function (error) { | |
if (error.code !== 'ECONNRESET') console.error(error, req.url) | |
reqd.dispose() | |
}) | |
next() | |
} |
var uuid = require('node-uuid'), // npm install node-uuid | |
crypto = require('crypto'); | |
var UUID_NUM = 1000000; | |
var uuid_table = {}; |
The idea is to have nginx installed and node installed. I will extend this gist to include how to install those as well, but at the moment, the following assumes you have nginx 0.7.62 and node 0.2.3 installed on a Linux distro (I used Ubuntu).
In a nutshell,
So for example, www.foo.com request comes and your css, js, and images get served thru nginx while everything else (the request for say index.html or "/") gets served through node.