most of these require logout/restart to take effect
# Enable character repeat on keydown
defaults write -g ApplePressAndHoldEnabled -bool false
# Set a shorter Delay until key repeat
// require modules | |
var express = require('express'), | |
i18n = require('i18n'), | |
hbs = require('hbs'), | |
app = module.exports = express(); | |
i18n.configure({ | |
locales: ['en', 'fr'], | |
cookie: 'locale', | |
directory: "" + __dirname + "/locales" |
Chris Veness created a really great gist that shares code to encrypt and decrypt data using the Web Crypto API here.
This gist breaks down the code in that gist step by step, detailing a real-world scenario with actual data.
It might be helpful to have that gist open in another tab and use this gist to walk through each line of code.
One interesting use case for this would be to encrypt on a client, and then decrypt in the cloud with something like a Lambda function. In order to do this, you could use Node's latest version as of this gist, version 15, which includes a webcrypto
module that's designed to be a Node implementation of the Web Crypto API. Lambdas can't use v15 by default -- however, you can create a custom Lambda layer that contains v15.
{"version":3,"sources":["app/public/scss/style.css"],"names":["'UTF-8'","url(","'https://fonts.googleapis.com/css?family=Montserrat:400,700'","/*!\n * Font Awesome 4.7.0 by @davegandy - http://fontawesome.io - @fontawesome\n * License - http://fontawesome.io/license (Font: SIL OFL 1.1, CSS: MIT License)\n */","/* FONT PATH\n * -------------------------- */","@font-face ","font-family","'FontAwesome'","src","'../fonts/fontawesome-webfont.eot?v=4.7.0'","'../fonts/fontawesome-webfont.eot?#iefix&v=4.7.0'","format(","'embedded-opentype'","'../fonts/fontawesome-webfont.woff2?v=4.7.0'","'woff2'","'../fonts/fontawesome-webfont.woff?v=4.7.0'","'woff'","'../fonts/fontawesome-webfont.ttf?v=4.7.0'","'truetype'","'../fonts/fontawesome-webfont.svg?v=4.7.0#fontawesomeregular'","'svg'","font-weight","normal","font-style",".fa","display","inline-block","font","14","px","/","1","FontAwesome","font-size","inherit","text-rendering","auto","-webkit-font-smoothing","antialiased","-moz-osx-font-smoothing","grayscale","/* makes th |
(async function () { | |
const IN = "10:00"; | |
const OUT = "18:00"; | |
const OFFSET = 10; | |
const rand = (n) => n - Math.floor(Math.random() * (2 * n + 1)); | |
const offsetHour = (h, o) => { | |
let [hh, mm] = h.split(":"); | |
hh = Number(hh); |
{"version":3,"file":"style.css","sources":["style.scss","../web_modules/font-awesome/scss/font-awesome.scss","../web_modules/font-awesome/scss/_variables.scss","../web_modules/font-awesome/scss/_mixins.scss","../web_modules/font-awesome/scss/_path.scss","../web_modules/font-awesome/scss/_core.scss","../web_modules/font-awesome/scss/_larger.scss","../web_modules/font-awesome/scss/_fixed-width.scss","../web_modules/font-awesome/scss/_list.scss","../web_modules/font-awesome/scss/_bordered-pulled.scss","../web_modules/font-awesome/scss/_animated.scss","../web_modules/font-awesome/scss/_rotated-flipped.scss","../web_modules/font-awesome/scss/_stacked.scss","../web_modules/font-awesome/scss/_icons.scss","../web_modules/font-awesome/scss/_screen-reader.scss","utilities/_normalize.scss"],"sourcesContent":["\n//Fonts\n@import url('https://fonts.googleapis.com/css?family=Montserrat:400,700');\n\n//Modules\n@import '../web_modules/font-awesome/scss/font-awesome';\n@import 'utilities/normalize';\n\n//Generic\n\nbody {\n |
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon
with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
If you're using a high-end bluetooth headset on your Macbook Pro it's likely your mac is using an audio codec which favors battery efficiency over high quality. This results in a drastic degradation of sound, the SBC codec is the likely culprit, read more about it here.
https://zuomod.com/Umea-Arm-Chair-Iron-Gray?search=500341 | |
https://zuomod.com/Umea-Arm-Chair-Island-Blue?search=500342 | |
https://zuomod.com/Graham-End-Table-Walnut?search=101059 | |
https://zuomod.com/Fashion-Counter-Chair-Stone-Gray?search=100646 | |
https://zuomod.com/Fashion-Counter-Chair-White?search=100647 | |
https://zuomod.com/Homestead-Lounge-Chair-White-Pu?search=100766 | |
https://zuomod.com/Quilt-Armless-Dining-Chair-Black?search=100187 | |
https://zuomod.com/Quilt-Armless-Dining-Chair-White?search=100188 | |
https://zuomod.com/Quilt-Dining-Chair-Black?search=100189 | |
https://zuomod.com/Quilt-Dining-Chair-White?search=100190 |
<?xml version="1.0" encoding="UTF-8"?> | |
<module type="WEB_MODULE" version="4"> | |
<component name="NewModuleRootManager"> | |
<content url="file://$MODULE_DIR$" /> | |
<orderEntry type="inheritedJdk" /> | |
<orderEntry type="sourceFolder" forTests="false" /> | |
</component> | |
</module> |