Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uq4Vz-00Gxoy-N3 for pgsql-advocacy@arkaria.postgresql.org; Sun, 24 Aug 2025 06:47:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uq4Uz-001Aht-Ko for pgsql-advocacy@arkaria.postgresql.org; Sun, 24 Aug 2025 06:46:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uq4Uz-001Ahk-DN for pgsql-advocacy@lists.postgresql.org; Sun, 24 Aug 2025 06:46:42 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uq4Ux-001Yot-0x for pgsql-advocacy@lists.postgresql.org; Sun, 24 Aug 2025 06:46:41 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender :Reply-To:Content-ID:Content-Description; bh=JdK1aXb1OZTvATdWh5Vsy5Iphmzg1lFA4H/PkodqJvY=; b=jgecAVp0KDYO/rxNOExe+UimNV mAPw+gTcrv1WBQFa6hl6tFaoQ+DL+4AJK6h2I2RTxwuUjSybP8xQAVveXZmmTgA5UGrnBfGHzC2eG 6MfyRaouWszz/Rv1y/JB1q27kL/95SAduhfZ4Akkq69TlMhbTlE9WZnhC4P2WLrJZA8fnxHw1s+un HKxG9WzGdEfgVNwWyxpGq/tIDwnwBxfRsex5uwNrrFmNNCIDG/A5FNE9m5r6BVTkGyV96qwg5tjNT t778jX5MPvUvfwUYSGMB1plBVbeXvkwvyhZqtK/yqwU8uczy/AuBmxEClD/g5jylO9LFocvlbksEU yV8xObXQ==; Received: from meldrar.postgresql.org ([87.238.57.231] helo=webmail.postgresql.org) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uq4Ut-003MJU-3A; Sun, 24 Aug 2025 06:46:38 +0000 MIME-Version: 1.0 Date: Sun, 24 Aug 2025 16:46:35 +1000 From: Justin Clift To: Sarah Bedell Cc: pgsql-advocacy@lists.postgresql.org Subject: Re: Verify postgres template on Railway? In-Reply-To: References: Message-ID: <790d2856871f0fe7b14a78d5abf4cb5e@postgresql.org> X-Sender: justin@postgresql.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2025-08-21 23:21, Sarah Bedell wrote: > The ask: would someone from the Postgres community be interested in > participating in this partnership? > > If so, we'd like to 1) have you verify the template looks good to you > and > 2) add a tutorial on launching Postgres in Railway in the docs (we can > write it). As a general thought, it _might_ also be useful to consider the "automatic upgrade" PostgreSQL docker container as well: https://github.com/pgautoupgrade/docker-pgautoupgrade That one better suits environments where people don't care about sticking to a known version of PostgreSQL, and instead just want to ensure they're working on a supported version. If no-one else from the PostgreSQL Community wants to take the time to review your template, then feel free to reach out to me directly. I know someone in the pgautoupgrade dev group who probably might. They'd likely need a Railway account set up for them so they can test stuff out properly though and verify it's all good. :) Regards and best wishes, Justin Clift