Create a .pgpass file that will be used to provide the password for any libpq-based program for the matching hostname/port/database/user. That file should be chmod'd 0600.
> cat .pgpass
127.0.0.1:5433:database:user:password
Create a SSH tunnel: we open the local port 5433 and, out of the tunnel, go to localhost:5432. You probably really want localhost and not remote: your PostgreSQL database is probably accepting connections only from locahost.
> ssh -N -L 5433:localhost:5432 user@remote
| { | |
| "project": "site", | |
| "event_id": "ac7d8c1c34fc4630ad850ee518f1b9d1", | |
| "culprit": "my.module.my.function", | |
| "timestamp": "2013-09-19T17:41:36", | |
| "message": "SyntaxError: abcd!", | |
| "exception": [{ | |
| "type": "SyntaxError", | |
| "value": "efgh", | |
| "module": "__builtins__" |
| module Main (main) where | |
| import Data.Binary.Get | |
| import System.IO.Streams.Internal (InputStream (..)) | |
| import qualified System.IO.Streams as Streams | |
| import Data.ByteString (ByteString) | |
| import qualified Data.ByteString.Char8 as S | |
| import Data.IORef (IORef, newIORef, readIORef, writeIORef) |
| from ubuntu:12.04 | |
| maintainer Vo Minh Thu <noteed@gmail.com> | |
| run echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list | |
| run apt-get update | |
| # Install PostgreSQL (for the postgres user) | |
| run apt-get install -q -y postgresql-9.1 | |
| # Install OpenSSH (for scp) |
I have been interested in creating a simple service to backup files. At first, the service was mainly intended to save PostgreSQL WAL segment files and I thought to simply use the scp command to upload the files to a remote machine. Then putting some more thoughts in it, it felt like a nice well-defined project and possibly like a minimum viable product.
More precisely I decided to expose a service, scp@reesd.com (think about the similarity with git@github.com or git@bitbucket.org when using the SSH transport) that would allow users to use the regular scp command to save and restore files. When scp would complete an upload to Reesd, it would mean that Reesd has actually streamed the content to multiple backend machines.
Although useable, Reesd is not yet ready for commercial use. I have still some tools to write to automate its deployment and more importantly, make sure I can restore data quickly in the event a replica fails. That being said, I have be
This Gist shows how to use Open vSwitch to bridge Docker containers on two hosts. It is based on this blog post http://goldmann.pl/blog/2014/01/21/connecting-docker-containers-on-multiple-hosts/.
A similar Gist using Tinc instead of Open vSwitch is available: https://gist.github.com/noteed/11031504.
Docker is all the rage these days. I started to look at Docker seriously maybe around April last year. It has gained a lot of momentum and I think it's just the beginning. For instance new tools and services are created regularly, or Docker, inc. has not yet unveiled their exact commercial offering (and I think they have a very rich view about what it is possible to achieve with Docker).
When I started to build Reesd, I have directly used Docker. Even if it is not production-ready, or even if there is some risk that it might evolve
| """ | |
| Simple workflow engine. | |
| A workflow is a directed graph where nodes are activities. The returned | |
| value of an activity is used to dispatch on its outgoing transitions. | |
| Activities are functions, accepting a `state` argument. | |
| def ACTIVITY(state): | |
| pass |
This Gist is similar to https://gist.github.com/noteed/8656989 which uses Open vSwitch instead of Tinc.
Download the install.sh script and run it:
> https://gist.githubusercontent.com/noteed/11031504/raw/install.sh