Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/
<meta charset="UTF-8">
#!/bin/sh | |
### | |
# SOME COMMANDS WILL NOT WORK ON macOS (Sierra or newer) | |
# For Sierra or newer, see https://github.com/mathiasbynens/dotfiles/blob/master/.macos | |
### | |
# Alot of these configs have been taken from the various places | |
# on the web, most from here | |
# https://github.com/mathiasbynens/dotfiles/blob/5b3c8418ed42d93af2e647dc9d122f25cc034871/.osx |
build { | |
# ... | |
provisioner "shell" { | |
inline = [ | |
"echo 'debconf debconf/frontend select Noninteractive' | debconf-set-selections", | |
"sudo apt-get update", | |
"sudo apt-get dist-upgrade -o Dpkg::Options::=--force-confold -o Dpkg::Options::=--force-confdef -y --allow-downgrades --allow-remove-essential --allow-change-held-packages", | |
"sudo apt-get autoremove -y", | |
"sudo apt-get clean", |
{ | |
"meta": { | |
"theme": "classy" | |
}, | |
"basics": { | |
"firstName": "Brandon", | |
"lastName": "Brown", | |
"name": "Brandon Brown", | |
"email": "resume@brandonb.ca", | |
"phone": "", |
module.exports = (on, config) => { | |
// ... | |
const wpOptions = webpack.defaultOptions | |
wpOptions.webpackOptions.resolve = { | |
extensions: ['.ts', '.js'], | |
} | |
wpOptions.webpackOptions.module.rules.push({ | |
test: /\.ts$/, | |
exclude: [/node_modules/], |
#!/bin/bash | |
logo="$(tput setaf 2) | |
.~~. .~~. | |
'. \ ' ' / .'$(tput setaf 1) | |
.~ .~~~..~. $(tput sgr0) _ _ $(tput setaf 1) | |
: .~.'~'.~. : $(tput sgr0) ___ ___ ___ ___| |_ ___ ___ ___ _ _ ___|_|$(tput setaf 1) | |
~ ( ) ( ) ~ $(tput sgr0) | _| .'|_ -| . | . | -_| _| _| | | | . | |$(tput setaf 1) | |
( : '~'.~.'~' : ) $(tput sgr0) |_| |__,|___| _|___|___|_| |_| |_ | | _|_|$(tput setaf 1) | |
~ .~ ( ) ~. ~ $(tput sgr0) |_| |___| |_| $(tput setaf 1) |
From: http://run-node.com/littlest-database-that-could/
I've written numerous tiny databases. They don't have much features, but they don't need much features. Usually I'm looking for fast simple key/value stores and Node never disappoints. The point here is, why abstract key value store when JS gives us one for free, as it's most basic component: object.
Will it meet every need? No. But it will meet ALOT of scenarios.
In memory JS object lookups, were talking hundreds of thousands of lookups (you'll easily flood http before the db), and save hundreds of thousands of records in a JSON file written to disk. Not a 200ms r/t to some hosted Redis. Hey, that's fine if that's your thing.
Here's the requirements:
/** | |
* Modified from the Connect project: https://github.com/senchalabs/connect/blob/master/lib/middleware/errorHandler.js | |
* | |
* Flexible error handler, providing (_optional_) stack traces and logging | |
* and error message responses for requests accepting text, html, or json. | |
* | |
* Options: | |
* | |
* - `showStack` respond with both the error message and stack trace. Defaults to `false` | |
* - `showMessage`, respond with the exception message only. Defaults to `false` |
#!/bin/sh | |
# Usernames who will be using the Dropbox service | |
DROPBOX_USERS="username" | |
DAEMON=.dropbox-dist/dropboxd | |
start() { | |
echo "Starting dropbox..." | |
for dbuser in $DROPBOX_USERS; do |