Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XCY6O-0006A3-Ad for pgsql-pkg-docker@arkaria.postgresql.org; Wed, 30 Jul 2014 17:55:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XCY6N-0006f4-9z for pgsql-pkg-docker@arkaria.postgresql.org; Wed, 30 Jul 2014 17:55:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XCY6M-0006ey-SV for pgsql-pkg-docker@postgresql.org; Wed, 30 Jul 2014 17:55:46 +0000 Received: from mx-out.zmailcloud.com ([192.198.85.98] helo=mx-out-1.zmailcloud.com) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XCY6I-0000fh-Qg for pgsql-pkg-docker@postgresql.org; Wed, 30 Jul 2014 17:55:45 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 21D4656609E; Wed, 30 Jul 2014 12:55:41 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 0FEF4A034B; Wed, 30 Jul 2014 12:55:41 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AU9NjQOP-g63; Wed, 30 Jul 2014 12:55:40 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 6C380A0578; Wed, 30 Jul 2014 12:55:40 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 52869A0572; Wed, 30 Jul 2014 12:55:40 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yG-NBb4bQdMz; Wed, 30 Jul 2014 12:55:40 -0500 (CDT) Received: from [172.47.23.104] (50-0-190-100.dsl.dynamic.sonic.net [50.0.190.100]) by smtp-out-1.01.com (Postfix) with ESMTPSA id B55D2A034B; Wed, 30 Jul 2014 12:55:39 -0500 (CDT) Message-ID: <53D9319A.7080708@agliodbs.com> Date: Wed, 30 Jul 2014 10:55:38 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Joseph Ferguson CC: Postgres-Docker Mailing List Subject: Re: SSH-free PostgreSQL References: <53D7E53A.5080505@agliodbs.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-docker Precedence: bulk Sender: pgsql-pkg-docker-owner@postgresql.org On 07/29/2014 12:55 PM, Joseph Ferguson wrote: > Overall this is a solid idea. While I am not terribly familiar with > postgres replication, couldn't the MASTER string be derived from > --link environment variables on the replica slave? It would at least > have the ip address and port from the ENV. We would also want to make > sure if they provide a ROLE for replica that they also provide the > other necessary parts (like the link if that fulfills the connection > string). There is a similar check in the official wordpress image (to > check for the mysql --link) [1]. Question: how does --link work if the two dockers are on different machines? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-pkg-docker