$ git clone https://github.com/cockpit-project/cockpit.git
$ cd cockpit
$ curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
$ sudo apt-get install -y nodejs
| #include <stdio.h> | |
| int main() | |
| { | |
| int a = 42; | |
| printf("%d\n", a); | |
| return 0; | |
| } | |
| #!/usr/bin/env bash | |
| # A basic Self Signed SSL Certificate utility | |
| # by Andrea Giammarchi @WebReflection | |
| # https://www.webreflection.co.uk/blog/2015/08/08/bringing-ssl-to-your-private-network | |
| # # to make it executable and use it | |
| # $ chmod +x certificate | |
| # $ ./certificate # to read the how-to |
SSL is an important security and privacy feature for all websites. Its details are outlined in this wikipedia [article] ("http://en.wikipedia.org/wiki/Secure_Sockets_Layer"). At Scibler, we use SSL certificates, encrypting all traffic to and fro from our servers. SSL is a public-key based asymmetric encryption scheme for symmetric key exchange. Symmetric keys are used for payload encryption. On our servers, we use embedded jetty (ring jetty adapter), with the clojure [ring] (https://github.com/ring-clojure) library to handle the http specific functionality.
This is a tutorial about installing SSL certificates on jetty webservers. SSL certificates are X.509 certificates that can be self-signed (authorized by Scibler) or can be signed by trusted third-parties. Trusted third-party certificates are the ones that a Internet user and browsers trust the most. Trusted third-party certification authorities issue certificates per domain and charge a nominal yearly fee.
####Pre-Requisites
| ES7 | core.async |
|---|---|
async function() {...} |
(fn [] (go ...)) |
await ... |
(<! ...) |
await* or Promise.all(...) |
(doseq [c ...] (<! c)) |
| (ns example.api.google | |
| (:require [cemerick.url :as url] | |
| [cheshire.core :as json] | |
| [clj-jwt.core :as jwt] | |
| [clj-jwt.key :as key] | |
| [clj-time.core :as time] | |
| [clj-http.client :as http] | |
| [clojure.string :as str]) | |
| (:import java.io.StringReader)) |
| (ns ... | |
| (:import [goog.net XmlHttp XmlHttpFactory]) | |
| (:require [cljs.nodejs :as nodejs])) | |
| (def xml-http-request | |
| (-> (nodejs/require "xmlhttprequest") | |
| (.. -XMLHttpRequest))) | |
| (defn NodeXhrFactory [] | |
| (this-as this (.call XmlHttpFactory this))) |
sudo zpool create -f zroot /dev/sdaX
sudo zfs create -o mountpoint=/var/lib/docker zroot/docker
/etc/defaults/docker(Serial port or com port? - Serial ports are often refered as COM ports. It is the same to be short. You can read abut it in the Wiki article )
A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats. The link points back at them.
If you are talking about the aspect of pattern matching that acts as a conditional based upon structure, I'm not a big fan. I feel about them the way I do about switch statements - they're brittle and