Guidelines:DualHost - Revision history

Dominic: /* Configuring Key-based Login */

2026-02-04T07:52:03Z

Configuring Key-based Login

← Older revision		Revision as of 07:52, 4 February 2026
Line 71:		Line 71:
	</syntaxhighlight>		</syntaxhighlight>

	Verify that you can SSH-login from the App Host to the DB Host (via private IP), as user ''eden'':		Verify that you can use this key to SSH-login from the App Host to the DB Host (via private IP), as user ''eden'':

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">

Dominic at 07:50, 4 February 2026

2026-02-04T07:50:36Z

Show changes

Dominic: /* Configure Host-based Access */

2026-02-02T23:26:39Z

Configure Host-based Access

← Older revision		Revision as of 23:26, 2 February 2026
Line 100:		Line 100:
	'''''Note:''' if your DB Host is behind a firewall, access from this IP/subnet to the port 5432 must be allowed. Adjust your firewall configuration as necessary.''		'''''Note:''' if your DB Host is behind a firewall, access from this IP/subnet to the port 5432 must be allowed. Adjust your firewall configuration as necessary.''

	Further, you must tell PostgreSQL to listen on the private IP of the DB Host. For that, edit the file <code>/etc/postgresql/17/main/postgresql.conf</code>, and modify the listen_address setting, adding the private IP of the DB Host:		Further, you must tell PostgreSQL to listen on the private IP of the DB Host. For that, edit the file <code>/etc/postgresql/17/main/postgresql.conf</code>, and modify the <code>listen_address</code> setting, adding the private IP of the DB Host:

	<syntaxhighlight lang="python">		<syntaxhighlight lang="python">

Dominic: /* Prerequisites and Terminology */

2026-02-02T23:24:53Z

Prerequisites and Terminology

← Older revision		Revision as of 23:24, 2 February 2026
Line 19:		Line 19:
	</pre>		</pre>

	...so that you have them readily at hand when walking through this guide. We will use designations like ''<apphost-public-ip>'', for instance, to refer to the public IP of the App Host.		...so that you have them readily at hand when walking through this guide. We will use designations like ''<apphost-public-ip>'', for instance, to refer to the public IP of the App Host. In these places, replace the designation with the respective IP address.

	Make sure that you have a '''DNS A-record''' set up for the public IP of the App Host, e.g. in the '''FQDN''' (fully qualified domain name) "eden.example.com", the "eden" part constitutes the '''hostname''', and "example.com" the '''domain'''. Make a note of these details, too:		Make sure that you have a '''DNS A-record''' set up for the public IP of the App Host, e.g. in the '''FQDN''' (fully qualified domain name) "eden.example.com", the "eden" part constitutes the '''hostname''', and "example.com" the '''domain'''. Make a note of these details, too:

Dominic: /* Prerequisites and Terminology */

2026-02-02T23:22:03Z

Prerequisites and Terminology

← Older revision		Revision as of 23:22, 2 February 2026
Line 21:		Line 21:
	...so that you have them readily at hand when walking through this guide. We will use designations like ''<apphost-public-ip>'', for instance, to refer to the public IP of the App Host.		...so that you have them readily at hand when walking through this guide. We will use designations like ''<apphost-public-ip>'', for instance, to refer to the public IP of the App Host.

	Make sure that you have a '''DNS A-record''' set up for the public IP of the App Host, e.g. in the '''FQDN''' (fully qualified domain name) "eden.example.com", the "eden" part constitutes the '''hostname''', and "example.com" the '''domain'''. ~~Note~~ these details ~~down~~:		Make sure that you have a '''DNS A-record''' set up for the public IP of the App Host, e.g. in the '''FQDN''' (fully qualified domain name) "eden.example.com", the "eden" part constitutes the '''hostname''', and "example.com" the '''domain'''. Make a note of these details, too:

	<pre>		<pre>

Dominic: /* Prerequisites and Terminology */

2026-02-02T23:21:43Z

Prerequisites and Terminology

← Older revision		Revision as of 23:21, 2 February 2026
Line 21:		Line 21:
	...so that you have them readily at hand when walking through this guide. We will use designations like ''<apphost-public-ip>'', for instance, to refer to the public IP of the App Host.		...so that you have them readily at hand when walking through this guide. We will use designations like ''<apphost-public-ip>'', for instance, to refer to the public IP of the App Host.

	Make sure that you have a '''DNS A-record''' set up for the public IP of the App Host, e.g. in the '''FQDN''' (fully qualified domain name) "eden.example.com", the "eden" part constitutes the '''hostname''', and "example.com" the '''domain''':		Make sure that you have a '''DNS A-record''' set up for the public IP of the App Host, e.g. in the '''FQDN''' (fully qualified domain name) "eden.example.com", the "eden" part constitutes the '''hostname''', and "example.com" the '''domain'''. Note these details down:

	<pre>		<pre>

Dominic: /* Dual Host Setup */

2026-02-02T23:20:09Z

Dual Host Setup

← Older revision		Revision as of 23:20, 2 February 2026
Line 4:		Line 4:
	* ''new in Eden-6.2 (not yet released)''		* ''new in Eden-6.2 (not yet released)''

	In certain situations, you may want to deploy Eden with a database on a separate host. Follow these steps for Debian/Linux:		In certain situations, you may want to deploy Eden with the database on a separate host. Follow these steps for Debian/Linux:

	== Prerequisites and Terminology ==		== Prerequisites and Terminology ==

Dominic: /* Configure Host-based Access */

2026-02-02T23:18:42Z

Configure Host-based Access

← Older revision		Revision as of 23:18, 2 February 2026
Line 100:		Line 100:
	'''''Note:''' if your DB Host is behind a firewall, access from this IP/subnet to the port 5432 must be allowed. Adjust your firewall configuration as necessary.''		'''''Note:''' if your DB Host is behind a firewall, access from this IP/subnet to the port 5432 must be allowed. Adjust your firewall configuration as necessary.''

	Further, you must tell PostgreSQL to listen on the private IP of the DB Host. For that, edit the file <code>/etc/postgresql/17/main/postgresql.conf</code>, and modify the ~~listen_addresses~~ setting, adding the private IP of the DB Host:		Further, you must tell PostgreSQL to listen on the private IP of the DB Host. For that, edit the file <code>/etc/postgresql/17/main/postgresql.conf</code>, and modify the listen_address setting, adding the private IP of the DB Host:

	<syntaxhighlight lang="python">		<syntaxhighlight lang="python">

Dominic: /* Dual Host Setup */

2026-02-02T23:13:38Z

Dual Host Setup

← Older revision		Revision as of 23:13, 2 February 2026
Line 2:		Line 2:

	= Dual Host Setup =		= Dual Host Setup =
			* ''new in Eden-6.2 (not yet released)''

	In certain situations, you may want to deploy Eden with a database on a separate host. Follow these steps for Debian/Linux:		In certain situations, you may want to deploy Eden with a database on a separate host. Follow these steps for Debian/Linux:

Dominic at 19:43, 2 February 2026

2026-02-02T19:43:29Z

← Older revision		Revision as of 19:43, 2 February 2026
Line 5:		Line 5:
	In certain situations, you may want to deploy Eden with a database on a separate host. Follow these steps for Debian/Linux:		In certain situations, you may want to deploy Eden with a database on a separate host. Follow these steps for Debian/Linux:

	=== Prerequisites and Terminology ===		== Prerequisites and Terminology ==

	This guideline assumes that you have two hosts running on Debian/Linux - we will use the '''App Host''' and '''DB Host''' designations here to distinguish between the two.		This guideline assumes that you have two hosts running on Debian/Linux - we will use the '''App Host''' and '''DB Host''' designations here to distinguish between the two.
Line 30:		Line 30:
	This guideline further assumes that you have set up the servers for key-based SSH login (see [[Guidelines:SecureOperation]]) with a non-privileged user account ''serveradm'' (replace this with the actual user name as required).		This guideline further assumes that you have set up the servers for key-based SSH login (see [[Guidelines:SecureOperation]]) with a non-privileged user account ''serveradm'' (replace this with the actual user name as required).

	=== Preparing the Servers ===		== Preparing the Servers ==

	First, we need to setup an additional key pair on the App Host, for ''edenctl'' to login at the DB Host. On your local machine, generate a key pair with:		First, we need to setup an additional key pair on the App Host, for ''edenctl'' to login at the DB Host. On your local machine, generate a key pair with:
Line 73:		Line 73:
	</syntaxhighlight>		</syntaxhighlight>

	=== Installing PostgreSQL ===		== Installing PostgreSQL ==

	On the DB Host, make yourself <code>root</code>:		On the DB Host, make yourself <code>root</code>:
Line 113:		Line 113:
	Logout from the DB Host, going back to the App Host.		Logout from the DB Host, going back to the App Host.

	=== Setting Up Eden ===		== Setting Up Eden ==

	Copy the Eden DEB-package to the App Host - either using <code>scp</code> from your local machine, or <code>wget</code> to fetch it from GitHub, e.g.:		Copy the Eden DEB-package to the App Host - either using <code>scp</code> from your local machine, or <code>wget</code> to fetch it from GitHub, e.g.: