start new:
tmux
start new with session name:
tmux new -s myname
Summary: use good/established messaging patterns like Enterprise Integration Patterns. Don't make up your own. Don't expose transport implementation details to your application.
As much as possible, I prefer to hide Rabbit's implementation details from my application. In .Net we have a Broker abstraction that can communicate through a lot of different transports (rabbit just happens to be our preferred one). The broker allows us to expose a very simple API which is basically:
#! /usr/bin/env bash | |
set -o errexit | |
sudo apt-get update && sudo apt-get upgrade | |
install="sudo apt-get install -y -q" | |
update="sudo apt-get update -q" | |
# setup install directory | |
mkdir -p /tmp/install |
task :generate_engine do | |
# Get name sent from console | |
name = ENV['name'].downcase | |
# Store useful paths | |
engine_path = "engines/#{name}" | |
dummy_path = 'spec/dummy' | |
lib_files_path = 'lib/tasks/files' | |
dummy_relative_path = "#{engine_path}/#{dummy_path}" |