| brew uninstall --force --ignore-dependencies ffmpeg | |
| brew install --ignore-dependencies chromaprint | |
| brew install amiaopensource/amiaos/decklinksdk | |
| brew cask install xquartz | |
| options=$(brew options homebrew-ffmpeg/ffmpeg/ffmpeg | grep -vE '\s' | grep -- '--with-' | grep -vi game-music-emu | tr '\n' ' ') | |
| brew install homebrew-ffmpeg/ffmpeg/ffmpeg ${options} |
| const MY_DOMAIN = "example.com" | |
| const START_PAGE = "https://www.notion.so/example" | |
| addEventListener('fetch', event => { | |
| event.respondWith(fetchAndApply(event.request)) | |
| }) | |
| const corsHeaders = { | |
| "Access-Control-Allow-Origin": "*", | |
| "Access-Control-Allow-Methods": "GET, HEAD, POST,PUT, OPTIONS", |
| _video_file="${1}" | |
| ffmpeg -i $_video_file -vf palettegen pal.png | |
| ffmpeg -i $_video_file -i pal.png -lavfi paletteuse=bayer_scale=4:dither=bayer -r 18 video.gif |
| import Html exposing (Html, Attribute) | |
| import Html | |
| import Html.Attributes | |
| import Html.Events exposing (..) | |
| import List | |
| import String | |
| ------------------ | |
| --- HELPER CODE -- | |
| ------------------ |
| This note explains how to build Postgres from source and setup to debug it using LLDB on a Mac. I used this technique to research this article: | |
| http://patshaughnessy.net/2014/10/13/following-a-select-statement-through-postgres-internals | |
| 1. Shut down existing postgres if necessary - you don’t want to mess up your existing DB or work :) | |
| $ ps aux | grep postgres | |
| pat 456 0.0 0.0 2503812 828 ?? Ss Sun10AM 0:11.59 postgres: stats collector process | |
| pat 455 0.0 0.0 2649692 2536 ?? Ss Sun10AM 0:05.00 postgres: autovacuum launcher process | |
| pat 454 0.0 0.0 2640476 304 ?? Ss Sun10AM 0:00.74 postgres: wal writer process | |
| pat 453 0.0 0.0 2640476 336 ?? Ss Sun10AM 0:00.76 postgres: writer process |
| # !/bin/bash | |
| # Copyright (c) 2011 Float Mobile Learning | |
| # http://www.floatlearning.com/ | |
| # | |
| # Permission is hereby granted, free of charge, to any person obtaining | |
| # a copy of this software and associated documentation files (the "Software"), | |
| # to deal in the Software without restriction, including without limitation | |
| # the rights to use, copy, modify, merge, publish, distribute, sublicense, | |
| # and/or sell copies of the Software, and to permit persons to whom the |
Dashing widget to display the next and some subsequent Google Calendar events using the Google Calendar API v3.
I use this widget to display my shift calendar - see the screenshot below
This widget works with API v3 and requires a service account to be set up via the Google Developer's Console. Once a project is set up, enable the Calendar API. On the Credentials page create a new OpenID and download the p12 key file - set up the path to this file in the job file and grant the email address access to the relevant calendar.
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.
This is a fork from the original CoreOS cloud formation template. It adds two EBS disks of 30G, mounted to /var/lib/docker.
This is intended to be used with an m3.large machine which comes with 30G of SSD.
The reason I add two of 30 and not one of 60 is because a BTRFS limitation.
You can use the "btrfs add" approach in the units to create a BTRFS raid.