NOTE: this is out of date - refer to moby/moby#9694
Here is a preview build of two new features we’re working on concurrently: container grouping (docker groups) and stack composition (docker up). Together, they will eventually form a complete replacement for Fig.
| #!/bin/bash | |
| cmd-hello() { | |
| declare desc="Displays a friendly hello" | |
| declare firstname="$1" lastname="$2" | |
| echo "Hello, $firstname $lastname." | |
| } | |
| cmd-help() { | |
| declare desc="Shows help information for a command" |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| App configuration in environment variables: for and against | |
| For (some of these as per the 12 factor principles) | |
| 1) they are are easy to change between deploys without changing any code | |
| 2) unlike config files, there is little chance of them being checked | |
| into the code repo accidentally | |
| 3) unlike custom config files, or other config mechanisms such as Java |
| #!/usr/bin/env ruby | |
| # | |
| # Syncs Ruby binstubs for ruby-communal-gems. | |
| # Run this everytime you install a new Ruby, or when you install a new gem | |
| # with a bin/ command. (ie, when you typically do rbenv rehash) | |
| # | |
| # See: https://github.com/tpope/rbenv-communal-gems/issues/5 | |
| # | |
| require 'fileutils' |
| # Our base formatters | |
| (-> | |
| checkElementActive = () -> | |
| selection = window.getSelection() | |
| node = undefined | |
| node = selection.getRangeAt(0).startContainer.parentNode if selection.rangeCount > 0 | |
| node and node.nodeName is this.title.toUpperCase() | |
| formatBlockOnClick = () -> |
| # sample config file | |
| [do] | |
| 198.199.74.236 tinc_ip=10.1.1.1 hostname=ca_1_1 tinc_connectto=ca_2_2 | |
| 192.34.60.13 tinc_ip=10.1.1.2 hostname=ca_1_2 tinc_connectto=ca_1_1 | |
| 198.199.70.163 tinc_ip=10.1.1.3 hostname=ca_1_3 tinc_connectto=ca_1_2 | |
| 198.199.71.204 tinc_ip=10.1.2.1 hostname=ca_2_1 tinc_connectto=ca_1_3 | |
| 198.199.70.208 tinc_ip=10.1.2.2 hostname=ca_2_2 tinc_connectto=ca_2_1 |
VMware ESXi includes a built in VNC server that can be used to access a VMs console for manipulation via automated tools (e.g., veewee) or by users on platforms where the vSphere Client is not supported. In ESXi 5.x, the built-in firewall does not allow VNC traffic to be received by the VNC server, even when an individual VM is configured to support this configuration. To complete this activity, the firewall has to be modified to allow the appropriate ports.
The below script can be run via the ESXi command line to setup the firewall rules necessary to run VNC. A few items to note:
/etc/rc.local (ESXi 5.0) or `/etc/rc.local
| /** | |
| The idea here is that all changes to your new object can be observed | |
| */ | |
| Ember.View.extend({ | |
| model: Ember.StalkableObject.create(), | |
| saveModel: Ember.observer(function () { | |
| /** do some fancy stuff to save changes to your model */ | |
| }, 'model.@properties') | |
| }); |
This gist was writen in 2012 and it was solving specific problem in Rails & SimpleForm. Some fellow developers were pointing out this may be out dated concept. That's why I advise everyone to read comment section bellow to have a full grasp of alternative solutions
other sources that may be helpful to understand why this may not be best idea: