以下の情報を元に Galera と GR のレプリケーションの違いをまとめたもの。
| brew install ffmpeg --with-fdk-aac --with-ffplay --with-freetype --with-libass --with-libquvi --with-libvorbis --with-libvpx --with-opus --with-x265 | |
| # Streaming with FFMPEG | |
| # https://trac.ffmpeg.org/wiki/StreamingGuide | |
| ffmpeg -f avfoundation -i "1:0" -c:v libx265 -preset fast -c:a libfdk_aac -b:a 160k test.mkv |
| Install Homebrew OS X package manager: | |
| /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" | |
| Install ffmpeg with x265 support: | |
| brew install ffmpeg --with-fdk-aac --with-ffplay --with-freetype --with-libass --with-libquvi --with-libvorbis --with-libvpx --with-opus --with-x265 | |
| Convert video to x265: | |
| ffmpeg -i input -c:v libx265 -preset medium -crf 28 -c:a aac -b:a 128k output.mp4 | |
| Uninstall ffmpeg: |
Kafka acts as a kind of write-ahead log (WAL) that records messages to a persistent store (disk) and allows subscribers to read and apply these changes to their own stores in a system appropriate time-frame.
Terminology:
| module golo.x | |
| import io.vertx.core.Vertx | |
| import io.vertx.core.http.HttpServer | |
| import io.vertx.ext.web.Router | |
| import io.vertx.ext.web.handler | |
| let vertx = Vertx.vertx() | |
| function createHttpServer = { |
Examples of getting certificates from Let's Encrypt working on Apache, NGINX and Node.js servers.
I chose to use the manual method, you have to make a file available to verify you own the domain. Follow the commands from running
git clone https://github.com/letsencrypt/letsencrypt
cd letsencrypt
TL;DR - smelly software engineer discusses using rethinkdb changefeeds for building caches, breaks hearts, shaves the cheerleader, shaves the world.
Let's talk about caches.
Imagine that you build UIs for an ecommerce company, possibly in a fancy office with free coffee and whatnot. You've just been asked to build a way for the marketing / sales folks to change landing pages whenever they're running campaigns. After a number of angry discussions involving the ux team about what they can and cannot change, you settle on a 'document' format for these pages. It could be json describing a tree of widgets of banners and carousels, or html, or yaml, or whatever. Maybe you also invent a dsl that marks out parts of the document as dynamic, based on request parameters or something. I dunno, I'm not your boss. You build a little ui over the weekend (with react? maybe!) that lets these folks login, drag and drop their banners, maybe upload an image or two, and save to database.
Yo
| let timeout = 1000; | |
| /** | |
| * Create a custom observable that creates a XHR request and returns complete when the promise is fulfilled | |
| */ | |
| let observable = Rx.Observable.create((o) => { | |
| dataService.fetch('test.json') | |
| .then((data) => { | |
| o.onNext(data); | |
| o.onCompleted(); |
Typing vagrant from the command line will display a list of all available commands.
Be sure that you are in the same directory as the Vagrantfile when running these commands!
vagrant init -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)