| (defmacro assert-all | |
| [& pairs] | |
| `(do (when-not ~(first pairs) | |
| (throw (IllegalArgumentException. | |
| (str (first ~'&form) " requires " ~(second pairs) " in " ~'*ns* ":" (:line (meta ~'&form)))))) | |
| ~(let [more (nnext pairs)] | |
| (when more | |
| (list* `assert-all more))))) | |
| (defmacro when-let* |
替换上你的login_token，域名ID，记录ID等参数，就可以运行了。 会在后台一直运行，每隔30秒检查一遍IP，如果修改了就更新IP。
获得domain_id可以用curl
curl -k https://dnsapi.cn/Domain.List -d "login_token=xxxxx,xxxxxxxx&format=json" | python -m json.tool
获得record_id类似
curl -k https://dnsapi.cn/Record.List -d "login_token=xxxxx,xxxxxxxx&domain_id=xxx&format=json" | python -m json.tool
| ;; vars since 1.4 in core | |
| (for [[n v] (ns-publics 'clojure.core) :let [since (:added (meta v))] :when (= since "1.4")] n) |
| (comment ; Fun with transducers, v2 | |
| ;; Still haven't found a brief + approachable overview of Clojure 1.7's new | |
| ;; transducers in the particular way I would have preferred myself - so here goes: | |
| ;;;; Definitions | |
| ;; Looking at the `reduce` docstring, we can define a 'reducing-fn' as: | |
| (fn reducing-fn ([]) ([accumulation next-input])) -> new-accumulation | |
| ;; (The `[]` arity is actually optional; it's only used when calling | |
| ;; `reduce` w/o an init-accumulator). |
| (require '[clojure.core.async :as a]) | |
| (def xform (comp (map inc) | |
| (filter even?) | |
| (dedupe) | |
| (flatmap range) | |
| (partition-all 3) | |
| (partition-by #(< (apply + %) 7)) | |
| (flatmap flatten) | |
| (random-sample 1.0) |
| package eval | |
| import scala.reflect.runtime.currentMirror | |
| import scala.tools.reflect.ToolBox | |
| import java.io.File | |
| object Eval { | |
| def apply[A](string: String): A = { | |
| val toolbox = currentMirror.mkToolBox() |
| package object mail { | |
| implicit def stringToSeq(single: String): Seq[String] = Seq(single) | |
| implicit def liftToOption[T](t: T): Option[T] = Some(t) | |
| sealed abstract class MailType | |
| case object Plain extends MailType | |
| case object Rich extends MailType | |
| case object MultiPart extends MailType |
| #!/bin/sh | |
| # linux firewall/forwarding | |
| modprobe iptable_nat | |
| echo 1 | tee /proc/sys/net/ipv4/ip_forward | |
| iptables -t nat -A POSTROUTING -s 10.10.10.1/2 -o eth0 -j MASQUERADE | |
| # install openvpn | |
| apt-get update && apt-get install -y openvpn | |
| cd /etc/openvpn/ | |
| INSTANCE=$(curl http://169.254.169.254/latest/meta-data/public-hostname) | |
| openvpn --genkey --secret ${INSTANCE}.key |
| (require '[clojure.java.io :as io]) | |
| (require '[oauth.twitter :refer [oauth-client]]) | |
| (defn read-properties | |
| "Parse a properties file, convert the property keys to Clojure | |
| keywords and return as a Clojure map." | |
| [resource-name] | |
| (when-let [resource (io/resource resource-name)] | |
| (let [properties (java.util.Properties.)] | |
| (with-open [stream (io/input-stream resource)] |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
