| //! # A trie that can be saved to and loaded from a file | |
| //! | |
| //! This crate implements a Trie with char keys. | |
| //! The trie can be saved to and loaded from a file on the local filesystem. | |
| //! This allows the user to persist the trie between executions. | |
| //! | |
| //! Basic example: | |
| //! | |
| //! ```ignore | |
| //! let trie_file = "/path/to/trie-file"; |
| // default exports | |
| export default 42; | |
| export default {}; | |
| export default []; | |
| export default foo; | |
| export default function () {} | |
| export default class {} | |
| export default function foo () {} | |
| export default class foo {} |
| # Copyright 2017 The Kubernetes Authors. | |
| # | |
| # Licensed under the Apache License, Version 2.0 (the "License"); | |
| # you may not use this file except in compliance with the License. | |
| # You may obtain a copy of the License at | |
| # | |
| # http://www.apache.org/licenses/LICENSE-2.0 | |
| # | |
| # Unless required by applicable law or agreed to in writing, software | |
| # distributed under the License is distributed on an "AS IS" BASIS, |
| # Should work on all Debian based distros with systemd; tested on Ubuntu 16.04+. | |
| # This will by default install all plugins; you can customize this behavior on line 6. Selecting too many plugins can cause issues when downloading. | |
| # Run as root (or sudo before every line) please. Note this is not designed to be run automatically; I recommend executing this line by line. | |
| apt install curl | |
| curl https://getcaddy.com | bash -s personal dns,docker,dyndns,hook.service,http.authz,http.awses,http.awslambda,http.cache,http.cgi,http.cors,http.datadog,http.expires,http.filemanager,http.filter,http.forwardproxy,http.geoip,http.git,http.gopkg,http.grpc,http.hugo,http.ipfilter,http.jekyll,http.jwt,http.locale,http.login,http.mailout,http.minify,http.nobots,http.prometheus,http.proxyprotocol,http.ratelimit,http.realip,http.reauth,http.restic,http.upload,http.webdav,net,tls.dns.auroradns,tls.dns.azure,tls.dns.cloudflare,tls.dns.cloudxns,tls.dns.digitalocean,tls.dns.dnsimple,tls.dns.dnsmadeeasy,tls.dns.dnspod,tls.dns.dyn,tls. |
| # Should work on all Debian based distros with systemd; tested on Ubuntu 16.04+. | |
| # This will by default install all plugins; you can customize this behavior on line 6. Selecting too many plugins can cause issues when downloading. | |
| # Run as root (or sudo before every line) please. Note this is not designed to be run automatically; I recommend executing this line by line. | |
| apt install curl | |
| curl https://getcaddy.com | bash -s personal dns,docker,dyndns,hook.service,http.authz,http.awses,http.awslambda,http.cache,http.cgi,http.cors,http.datadog,http.expires,http.filemanager,http.filter,http.forwardproxy,http.geoip,http.git,http.gopkg,http.grpc,http.hugo,http.ipfilter,http.jekyll,http.jwt,http.locale,http.login,http.mailout,http.minify,http.nobots,http.prometheus,http.proxyprotocol,http.ratelimit,http.realip,http.reauth,http.restic,http.upload,http.webdav,net,tls.dns.auroradns,tls.dns.azure,tls.dns.cloudflare,tls.dns.cloudxns,tls.dns.digitalocean,tls.dns.dnsimple,tls.dns.dnsmadeeasy,tls.dns.dnspod,tls.dns.dyn,tls. |
| const crypto = require('crypto') | |
| const sign = (value, secret) => { | |
| return value + '.' + crypto | |
| .createHmac('sha256', secret + '') | |
| .update(value + '') | |
| .digest('base64') | |
| .replace(/\=+$/, '') | |
| } |
This tutorial was created by Shopify for internal purposes. We've created a public version of it since we think it's useful to anyone creating a GraphQL API.
It's based on lessons learned from creating and evolving production schemas at Shopify over almost 3 years. The tutorial has evolved and will continue to change in the future so nothing is set in stone.
Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".
Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).
Let's dig in:
This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.
While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.
| { | |
| "optimist": [], | |
| "entities": { | |
| "users": { | |
| "entities": { | |
| "11250": { | |
| "id": 11250, | |
| "id_str": "11250", | |
| "name": "Jeremy Keith", | |
| "screen_name": "adactio", |
