TrueNAS Project - Revision history

Lynn: /* The Environment */

2026-09-01T18:56:37Z

The Environment

← Older revision		Revision as of 18:56, 1 September 2026
Line 38:		Line 38:
	1. Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.		1. Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.
	2. For each stack execute the following commands:		2. For each stack execute the following commands:
	{{syntaxhighlight}}		<syntaxhighlight>
	cd [stack]~~<br~~		cd [stack]
	ln -s ../env env <~~br>~~		ln -s ../env env
	{{/syntaxhighlight}}		</syntaxhighlight>
	3. In stack, edit the container definitions to add the following two lines above the environment directive:<br>		3. In stack, edit the container definitions to add the following two lines above the environment directive:<br>
	{{syntaxhighlight}}		<syntaxhighlight>
	env_file:~~<br>~~		env_file:
	- ./env<~~br>~~		- ./env
	{{/syntaxhighlight}}		</syntaxhighlight>
	4. Deploy, or start, the stack		4. Deploy, or start, the stack

Lynn: /* The Environment */

2026-09-01T18:54:27Z

The Environment

← Older revision		Revision as of 18:54, 1 September 2026
Line 36:		Line 36:
	To implement assuming the standard location, the following steps are needed:		To implement assuming the standard location, the following steps are needed:

	# Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.		1. Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.
	# For each stack execute the following commands:~~<br>~~		2. For each stack execute the following commands:
	~~<br>~~		{{syntaxhighlight}}
	cd [stack]<br		cd [stack]<br
	ln -s ../env env <br>		ln -s ../env env <br>
	~~<br>~~		{{/syntaxhighlight}}
	# In stack, edit the container definitions to add the following two lines above the environment directive:<br>		3. In stack, edit the container definitions to add the following two lines above the environment directive:<br>
	~~<br>~~		{{syntaxhighlight}}
	env_file:<br>		env_file:<br>
	- ./env<br>		- ./env<br>
	~~<br>~~		{{/syntaxhighlight}}
	# Deploy, or start, the stack		4. Deploy, or start, the stack

	Since the environment is set during the startup, the environment isn't dynamic. A start, or redeployment, is necessary for the environment change to take effect. Only one option will be offered.		Since the environment is set during the startup, the environment isn't dynamic. A start, or redeployment, is necessary for the environment change to take effect. Only one option will be offered.

	~~Local~~ environment ~~definitions will override those taken from~~ the file.		The order of precedence is: environment directives, local .env file and then the global env file.

	Verify that the desired definitions are in effect using Portainer.		Verify that the desired definitions are in effect using Portainer.

Lynn: /* The Environment */

2026-09-01T18:51:36Z

The Environment

← Older revision		Revision as of 18:51, 1 September 2026
Line 37:		Line 37:

	# Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.		# Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.
	# For each stack execute the following commands:		# For each stack execute the following commands:<br>
	<~~syntaxhighlight lang=shell~~>		<br>
	cd [stack]		cd [stack]<br
	ln -s ../env env		ln -s ../env env <br>
	<~~/syntaxhighlight~~>		<br>
	# In stack, edit the container definitions to add the following two lines above the environment directive:		# In stack, edit the container definitions to add the following two lines above the environment directive:<br>
	<~~syntaxhighlight lang=shell~~>		<br>
	env_file:		env_file:<br>
	- ./env		- ./env<br>
	<~~/syntaxhighlight~~>		<br>
	# Deploy, or start, the stack		# Deploy, or start, the stack

Lynn: /* The Environment */

2026-09-01T18:49:51Z

The Environment

← Older revision		Revision as of 18:49, 1 September 2026
Line 38:		Line 38:
	# Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.		# Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.
	# For each stack execute the following commands:		# For each stack execute the following commands:
	<~~pre~~>		<syntaxhighlight lang=shell>
	cd [stack]		cd [stack]
	ln -s ../env env		ln -s ../env env
	</~~pre~~>		</syntaxhighlight>
	# In stack, edit the container definitions to add the following two lines above the environment directive:		# In stack, edit the container definitions to add the following two lines above the environment directive:
	<~~pre~~>		<syntaxhighlight lang=shell>
	env_file:		env_file:
	- ./env		- ./env
	</~~pre~~>		</syntaxhighlight>
	# Deploy, or start, the stack		# Deploy, or start, the stack

Lynn: /* The Environment */

2026-09-01T18:42:52Z

The Environment

← Older revision		Revision as of 18:42, 1 September 2026
Line 25:		Line 25:

	==Extensions and workarounds==		==Extensions and workarounds==
	===The Environment===		====The Environment====
	Following the system configuration instructions, dockge will be installed in the '''/mnt/tank/docker/dockge''' dataset. This location can be changed in the application definition of dockge in TrueNAS apps.Three datasets are defined under that location, data, secrets and stacks. Each stack that is created in the application has a directory under stacks.		Following the system configuration instructions, dockge will be installed in the '''/mnt/tank/docker/dockge''' dataset. This location can be changed in the application definition of dockge in TrueNAS apps.Three datasets are defined under that location, data, secrets and stacks. Each stack that is created in the application has a directory under stacks.

Lynn: /* The Environment */

2026-09-01T18:42:35Z

The Environment

← Older revision		Revision as of 18:42, 1 September 2026
Line 52:		Line 52:

	Local environment definitions will override those taken from the file.		Local environment definitions will override those taken from the file.

			Verify that the desired definitions are in effect using Portainer.


	Back to: [[Software on Linux Desktops]]		Back to: [[Software on Linux Desktops]]

Lynn: /* The Environment */

2026-09-01T18:41:34Z

The Environment

← Older revision		Revision as of 18:41, 1 September 2026
Line 47:		Line 47:
	- ./env		- ./env
	</pre>		</pre>
	# Deploy, or ~~restart~~, the stack		# Deploy, or start, the stack

	Since the environment is set during the startup, the environment isn't dynamic. A ~~restart~~, or redeployment, is necessary for the environment change to take effect.		Since the environment is set during the startup, the environment isn't dynamic. A start, or redeployment, is necessary for the environment change to take effect. Only one option will be offered.

	Local environment definitions will override those taken from the file.		Local environment definitions will override those taken from the file.

Lynn: /* The Environment */

2026-09-01T18:38:46Z

The Environment

← Older revision		Revision as of 18:38, 1 September 2026
Line 47:		Line 47:
	- ./env		- ./env
	</pre>		</pre>
	# Deploy the stack		# Deploy, or restart, the stack

	Since the environment is set during the startup, the environment isn't dynamic. A restart, or redeployment, is necessary for the environment change to take effect.		Since the environment is set during the startup, the environment isn't dynamic. A restart, or redeployment, is necessary for the environment change to take effect.

			Local environment definitions will override those taken from the file.


	Back to: [[Software on Linux Desktops]]		Back to: [[Software on Linux Desktops]]

Lynn: /* The Environment */

2026-09-01T18:37:01Z

The Environment

← Older revision		Revision as of 18:37, 1 September 2026
Line 42:		Line 42:
	ln -s ../env env		ln -s ../env env
	</pre>		</pre>
			# In stack, edit the container definitions to add the following two lines above the environment directive:
			<pre>
			env_file:
			- ./env
			</pre>
			# Deploy the stack

			Since the environment is set during the startup, the environment isn't dynamic. A restart, or redeployment, is necessary for the environment change to take effect.



	Back to: [[Software on Linux Desktops]]		Back to: [[Software on Linux Desktops]]

Lynn: /* The Environment */

2026-09-01T18:32:26Z

The Environment

← Older revision		Revision as of 18:32, 1 September 2026
Line 36:		Line 36:
	To implement assuming the standard location, the following steps are needed:		To implement assuming the standard location, the following steps are needed:

	# Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks.		# Create a file called env in '''/mnt/tank/docker/dockge/stacks'''. This file will contain all of the common definitions across the stacks. Edit the env file with all of the common definitions.
	# For each stack execute the following commands:		# For each stack execute the following commands:

	<pre>		<pre>
	cd [stack]		cd [stack]