This gist will drive you through creating a Docker 1.12 Swarm cluster (with Swarm mode) on AWS infrastructure.
You need a few things already prepared in order to get started. You need at least Docker 1.12 set up. I was using the stable version of Docker for mac for preparing this guide.
$ docker --version
Docker version 1.12.0, build 8eab29e
You also need Docker machine installed.
| /** | |
| * Summernote PasteClean | |
| * | |
| * This is a plugin for Summernote (www.summernote.org) WYSIWYG editor. | |
| * It will clean up the content your editors may paste in for unknown sources | |
| * into your CMS. It strips Word special characters, style attributes, script | |
| * tags, and other annoyances so that the content can be clean HTML with | |
| * no unknown hitchhiking scripts or styles. | |
| * | |
| * @author Jason Byrne, FloSports <jason.byrne@flosports.tv> |
Welcome to the sixth episode in a series of short screencasts about the Ruby neo4j gem. Previously we learned how to chain associations together to create queries which can hop across entities and use any part of the entire path to query records of interest. In this episode we dig deeper into the tools behind the magic. A familiarity with the Cypher query language is advised. See the show notes for a link to a Cypher tutorial.
As discussed previously, when we call associations we get a proxy object:
user.created_assets
There are two kinds of proxy objects: AssociationProxy and QueryProxy. The details aren't important for the moment, but behind the scenes both are causing a Query object to be built. We can see this Query object by calling the query method at any point:
user.created_assets.query
| 'use strict' | |
| var gulp, sass, babelify, browserify, watchify, source, util; | |
| gulp = require('gulp'); | |
| sass = require('gulp-sass'); | |
| babelify = require('babelify') | |
| browserify = require('browserify'); | |
| watchify = require('watchify'); | |
| source = require('vinyl-source-stream'); |
| # This is an example of the Stack Exchange Tier 1 HAProxy config | |
| # The only things that have been changed from what we are running are: | |
| # 1. User names have been removed | |
| # 2. All Passwords have been remove | |
| # 3. IPs have been changed to use the example/documentation ranges | |
| # 4. Rate limit numbers have been changed to randome numbers, don't read into them | |
| userlist stats-auth | |
| group admin users $admin_user | |
| user $admin_user insecure-password $some_password |
| # This is a Dragonfly data store using PostgreSQL Large Objects. It appears to work fine, | |
| # but I ended up using a different solution in my project. Anyway, here you go. | |
| # | |
| class PostgresDataStore | |
| def write(content, opts={}) | |
| data_oid = store_lo(content.data) | |
| meta_oid = store_lo(Marshal.dump(content.meta)) | |
| "#{data_oid}/#{meta_oid}" | |
| end |
| # to generate your dhparam.pem file, run in the terminal | |
| openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
This is just a jotting of notes on how to embed Faye into a single Rails process. Makes it nice to do simple real time things without the need for a separate Faye server/process.
Also uses Faye Redis to work across load balanced Rails apps.
You also need to copy the compiled javascript into vendor/assets/javascripts and include into application.js manifest.
Ignore the numbers in the file names... just used to add order to the Gist.
This uses the faye/faye Github repo at edc5b42f6560d31eae61caf00f6765a90e1818d1 since I wanted to use with the Puma rack server and that is only available in the master branch (until Faye 1.0)
Many of us spend many hours of our days using their terminal. Plus, we all have different tastes when it comes to color schemes. That's why the ability to change the color scheme of a terminal is one of its more important featuresl. Throughout this tutorial, I'll teach you how you can change the looks of your terminal, step by step.
This tutorial is aimed at elementary OS users, but it also works for any Ubuntu user. Start by installing dconf-tools:
sudo apt-get install dconf-tools
Secondly, you need to decide which theme you're going to apply. You can find dozens of terminal color schemes online, you can even design your own using this web application. Design the color scheme, hit "Get Scheme" and choose "Terminator". You'll get a raw text file with a background color, a foreground color and a palette. Those strings define your color scheme. In this tutorial, I'll post an