(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.
| editor.addKeyMap({ | |
| "Tab": function (cm) { | |
| if (cm.somethingSelected()) { | |
| var sel = editor.getSelection("\n"); | |
| // Indent only if there are multiple lines selected, or if the selection spans a full line | |
| if (sel.length > 0 && (sel.indexOf("\n") > -1 || sel.length === cm.getLine(cm.getCursor().line).length)) { | |
| cm.indentSelection("add"); | |
| return; | |
| } | |
| } |
| # post_loc.txt contains the json you want to post | |
| # -p means to POST it | |
| # -H adds an Auth header (could be Basic or Token) | |
| # -T sets the Content-Type | |
| # -c is concurrent clients | |
| # -n is the number of requests to run in the test | |
| ab -p post_loc.txt -T application/json -H 'Authorization: Token abcd1234' -c 10 -n 2000 http://example.com/api/v1/locations/ |
| app.all('*', function (req, res, next) { | |
| res.header("Access-Control-Allow-Origin", req.headers.origin); | |
| res.header("Access-Control-Allow-Credentials", true); | |
| res.header('Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE,OPTIONS'); | |
| res.header("Access-Control-Allow-Headers", "X-Requested-With, Content-Type, Authorization, Content-Length"); | |
| if (req.method == 'OPTIONS') { | |
| return res.send(200); | |
| } |
| # Node-WebKit CheatSheet | |
| # Download: https://github.com/rogerwang/node-webkit#downloads | |
| # Old Versions: https://github.com/rogerwang/node-webkit/wiki/Downloads-of-old-versions | |
| # Wiki: https://github.com/rogerwang/node-webkit/wiki | |
| # How: https://github.com/rogerwang/node-webkit/wiki/How-node.js-is-integrated-with-chromium | |
| # 1. Run your application. | |
| # https://github.com/rogerwang/node-webkit/wiki/How-to-run-apps |
(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.
| .SVGIcon { | |
| -webkit-font-smoothing: antialiased; | |
| -moz-osx-font-smoothing: grayscale; | |
| /* fix webkit/blink poor rendering issues */ | |
| transform: translate3d(0,0,0); | |
| /* it's better defined directly because of the cascade shit | |
| width: inherit; | |
| height: inherit; |
| À A | |
| Á A | |
| Â A | |
| Ã A | |
| Ä A | |
| Å A | |
| Æ A | |
| à a | |
| á a | |
| â a |
Yet another framework syndrome
| Name | Date | URL | Stars |
|---|---|---|---|
| Jake | April 2010 | https://github.com/mde/jake | 1000 |
| Brunch | January 2011 | http://brunch.io/ | 3882 |
| Ruby 2.1.0 in Production: known bugs and patches | |
| Last week, we upgraded the github.com rails app to ruby 2.1.0 in production. | |
| While testing the new build for rollout, we ran into a number of bugs. Most of | |
| these have been fixed on trunk already, but I've documented them below to help | |
| anyone else who might be testing ruby 2.1 in production. | |
| @naruse I think we should backport these patches to the ruby_2_1 branch and | |
| release 2.1.1 sooner rather than later, as some of the bugs are quite critical. | |
| I'm happy to offer any assistance I can to expedite this process. |
| # to generate your dhparam.pem file, run in the terminal | |
| openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |