How to setup next.js app on nginx with letsencrypt
next.js, nginx, reverse-proxy, ssl
1. Install nginx and letsencrypt
$ sudo apt-get update $ sudo apt-get install nginx letsencrypt
|// @name Stack Exchange hotness estimator|
|// @namespace http://vyznev.net/|
|// @description Estimates how highly each Stack Exchange question would rank on the Hot Network Questions list|
|// @author Ilmari Karonen|
|// @version 0.4.2|
|// @license Public domain|
|// @homepageURL http://meta.stackexchange.com/a/284933|
|// @match *://*.stackexchange.com/questions/*|
|// @match *://*.stackoverflow.com/questions/*|
|# Why? Education & zero redis-cli dependecy|
|# (it is a shame, however, that this functionality isn't a part of redis-cli... PR on the way)|
|if [ $# -lt "2" ]|
|echo "Call a Redis command with its last argument being file contents"|
|echo "Usage: $0 <Redis command> <keys and arguments for command> <payload>"|
The content from this GIST has been moved to official Azure Cache for Redis Documentation. The new location is https://docs.microsoft.com/azure/azure-cache-for-redis/cache-troubleshoot-client
Please update your bookmarks.
The CLR ThreadPool has two types of threads - "Worker" and "I/O Completion Port" (aka IOCP) threads.
ThreadPool.QueueUserWorkItem(…)methods. These threads are also used by various components in the CLR when work needs to happen on a background thread.
The thread pool provides new worker threads or I/O completion threads on demand (without any throttling) until it reaches the "Minimum" setting for each type of thread. By default, the minimum number of threads is set to the number of processors on a system.
Once the number of existing (busy) threads hits the "minimum" number of threads, the ThreadPool will throttle the rate at which is injects new threads to one thread per 500 milliseconds. This means that if your system gets a burst of work needing an IOCP thread, it will proces
[Google recently announced][poodle] that there is an exploit in SSLv3, this vulnerability is know as POODLE. There is no other option than to disable SSLv3 in order to combat this major flaw. There have already been [guides on how to disable this in different servers][guides]. But nothing excised for Node.js yet, until now. In order to resolve this for Node.js we need to use various of undocumented options and modules.
index.js file below you can see an example of how you can protect your HTTPS server
against the POODLE attack. It uses the
secureOptions option to pass in constants in to the
SSL context which is created by node.
|# Author: Pieter Noordhuis|
|# Description: Simple demo to showcase Redis PubSub with EventMachine|
|# Update 7 Oct 2010:|
|# - This example does *not* appear to work with Chrome >=6.0. Apparently,|
|# the WebSocket protocol implementation in the cramp gem does not work|
|# well with Chrome's (newer) WebSocket implementation.|
|# - rubygems: eventmachine, thin, cramp, sinatra, yajl-ruby|