This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
let update = { | |
$set: { | |
hello: { | |
world: 'anything' | |
} | |
} | |
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// the regex is generated using https://txt2re.com | |
// Time Stamp 1 | |
var re1='((?:2|1)\\d{3}(?:-|\\/)(?:(?:0[1-9])|(?:1[0-2]))(?:-|\\/)(?:(?:0[1-9])|(?:[1-2][0-9])|(?:3[0-1]))(?:T|\\s)(?:(?:[0-1][0-9])|(?:2[0-3])):(?:[0-5][0-9]):(?:[0-5][0-9]))'; | |
// Any Single Character 1 | |
var re2='(\\.)'; | |
// Any Single Digit 1 | |
var re3='(\\d)'; | |
// Any Single Digit 2 | |
var re4='(\\d)'; | |
// Any Single Digit 3 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TBD |
While I'm learning how to use Nginx, I was instructed to update the server_names_hash_bucket_size
(/etc/nginx/nginx.conf
) value from 32 to 64, but I don't understand why should I increase the value to 64.
References that have been read so far:
- See the Server names, Optimization section.
- See setting up hashes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
96048 silly gunzTarPerm extractEntry array/last.js | |
96049 silly gunzTarPerm modified mode [ 'array/last.js', 420, 436 ] | |
96050 silly gunzTarPerm extractEntry array/lastIndexOf.js | |
96051 silly gunzTarPerm modified mode [ 'array/lastIndexOf.js', 420, 436 ] | |
96052 silly gunzTarPerm extractEntry array/object.js | |
96053 silly gunzTarPerm modified mode [ 'array/object.js', 420, 436 ] | |
96054 silly gunzTarPerm extractEntry array/pull.js | |
96055 silly gunzTarPerm modified mode [ 'array/pull.js', 420, 436 ] | |
96056 silly gunzTarPerm extractEntry array/intersection.js | |
96057 silly gunzTarPerm modified mode [ 'array/intersection.js', 420, 436 ] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
docker build -t dockerhub-username/repository-name:0.10 . | |
docker push dockerhub-username/repository-name:0.10 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Secure sessions are easy, but it's not very well documented, so I'm changing that. | |
Here's a recipe for secure sessions in Node.js when NginX is used as an SSL proxy: | |
The desired configuration for using NginX as an SSL proxy is to offload SSL processing | |
and to put a hardened web server in front of your Node.js application, like: | |
[NODE.JS APP] <- HTTP -> [NginX] <- HTTPS -> [CLIENT] | |
To do this, here's what you need to do: |