It goes a little something like this:
rails new APP_NAME --database=postgresql --skip-test-unit
suspenders APP_NAME --skip-git true --skip-keeps true --force
Then comes a whole bunch of customizing for my likes:
- unicorn -> puma
# Key considerations for algorithm "RSA" ≥ 2048-bit
openssl genrsa -out server.key 2048
# Key considerations for algorithm "ECDSA" ≥ secp384r1
# List ECDSA the supported curves (openssl ecparam -list_curves)
import "dart:collection"; | |
class Tuple<A, B> { | |
A a; | |
B b; | |
Tuple(this.a, this.b); | |
} | |
void main() { |
Often referred to as the "swiss army of knife" for TCP/IP networking, [Netcat][1] is an extremely versatile Linux utility that allows you to do anything under the sun using TCP/UDP sockets. It is one of the most favorite tools for system admins when they need to do networking related troubleshooting and experimentation.
In this tutorial, I am sharing a few useful netcat examples, although the sky is the limit when it comes to possible netcat
use cases. If you are using netcat
regularly, feel free to share your use case.
Note that when you are binding to well-known ports (0-1023) with nc
, you need root privilege. Otherwise, run nc
as a normal user.
$ nc -vn 192.168.233.208 5000
List some crypto libraries for JavaScript out there. Might be a bit out dated. Scroll to the bottom.
http://www.w3.org/TR/WebCryptoAPI/
This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.
Located in alphabetical order (not prefer)
C
ab
), also designed as a more modern replacement, written in C
golang
)-module(elasticsearch). | |
-export([autocomplete/1, autocomplete/0, | |
search/1, search/0, | |
start/0, | |
stop/0, | |
loop/1]). | |
-on_load(start/0). | |
%% Return an autocomplete request | |
autocomplete() -> |
# | |
# CORS header support | |
# | |
# One way to use this is by placing it into a file called "cors_support" | |
# under your Nginx configuration directory and placing the following | |
# statement inside your **location** block(s): | |
# | |
# include cors_support; | |
# | |
# As of Nginx 1.7.5, add_header supports an "always" parameter which |