FGtatsuro FGtatsuro

Overview

This gist demonstrates how to run a docker container with nomad, using a wrapper script.

Why would you want to use this?

With the wrapper, we can more easily run the container in the way we need to and without being limited by Nomad's docker driver. For example, while Nomad will have great support for volumes in the future, it has no such support right now, and the driver does not expose a config parameter to tune the volumes mounted in the docker container. This is also a great way to use consul to lookup services before starting your app, or to retrieve credentials from Vault. When running legacy applications with nomad, the wrapper script is the place to put that type of look-up logic.

We use a wrapper script and the raw_exec driver to run the container with the parameters we need.

Limitations

CommonMark-py supports syntax of CommonMark. So, CommonMark-py doesn't support sphinx/reST role and directives.

References

ReCommonMark doc sample

MQTT とはなんだったのか

更新:	2017-05-09
作者:	@voluntas
バージョン:	3.14
URL:	http://voluntas.github.io/

MQTT をググって調べた人向け

Git ファイルの履歴を完全に削除する

秘密鍵など誤ってコミットしてしまった場合に履歴を完全に削除する手順
参考:6.4 Git のさまざまなツール - 歴史の書き換え

動作確認用にブランチを作成して試す

$ git checkout -b clean-key-file

動作確認用にブランチでgit filter-branchを実行

時雨堂 MQTT ブローカー開発ログまとめ

日時:	2015-01-10
作:	@voluntas
バージョン:	0.3.4
url:	http://voluntas.github.io/

注意

先輩に学ぶ HTTP Status Code

超雑にまとめました。修正してください。

登場人物

アプリケーション先輩: いつも忙しい。横に広がるのが得意(デブじゃない)。
後輩: 頼んでばっかしで役に立たない。
サーバー先輩: アプリケーション先輩と仲がいい。Unix Socket でつながるくらい仲良し。
プロクシ先輩: アプリケーション先輩とかサーバー先輩と後輩の間を取り持って代わりに伝えたりしてくれる。たまに勝手にレスポンスを書き換える。

	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	How to write python database driver
	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

	- https://pycon.jp/2016/ja/schedule/presentation/13/
	- https://www.youtube.com/watch?v=ax2WmQ_MSXs
	- https://togetter.com/li/1028521

	========================================
	Preface

	#!/usr/bin/env python
	# -- coding: utf-8 --

	from contextlib import contextmanager


	@contextmanager
	def ctxmgr():
	print('before')

	#!/bin/bash

	JENKINS_URL=$1
	NODE_NAME=$2
	NODE_SLAVE_HOME='/home/build/slave'
	EXECUTORS=1
	SSH_PORT=22
	CRED_ID=$3
	LABELS=build
	USERID=${USER}

	#!/usr/bin/env python

	# I was frustrated that no matter what buffer setting I passed to communicate,
	# I could not get stdout from my subprocess until the process had completed.
	# I googled around and came up with this, which illustrates the problem and a
	# solution.

	# http://stackoverflow.com/questions/2804543/read-subprocess-stdout-line-by-line
	# http://bugs.python.org/issue3907
	# http://docs.python.org/library/io.html