Nextcloud - Revision history

Pricey: /* App specific configuration */ Memories Hardware Acceleration

2026-05-19T17:41:45Z

App specific configuration: Memories Hardware Acceleration

← Older revision		Revision as of 17:41, 19 May 2026
Line 546:		Line 546:

	For easy deployment, there's the [https://apps.nextcloud.com/apps/richdocumentscode richdocumentscode app] which bundles the CODE server. While being less performant than a standalone deployment of the CODE server, this solution does not require an additional service to be deployed and managed externally from NextCloud. Unfortunately the richdocumentscode app bundles the CODE server as an AppImage and therefore does not work out of the box on NixOS. Follow https://github.com/NixOS/nixpkgs/issues/339798 if you want to get informed about packaging progress. Also CODE standalone is currently not packaged in nixpkgs (https://github.com/NixOS/nixpkgs/issues/218878).		For easy deployment, there's the [https://apps.nextcloud.com/apps/richdocumentscode richdocumentscode app] which bundles the CODE server. While being less performant than a standalone deployment of the CODE server, this solution does not require an additional service to be deployed and managed externally from NextCloud. Unfortunately the richdocumentscode app bundles the CODE server as an AppImage and therefore does not work out of the box on NixOS. Follow https://github.com/NixOS/nixpkgs/issues/339798 if you want to get informed about packaging progress. Also CODE standalone is currently not packaged in nixpkgs (https://github.com/NixOS/nixpkgs/issues/218878).

			=== Memories ===
			To enable hardware acceleration, nextcloud will need access to the graphics card with e.g:<syntaxhighlight lang="nix">
			users.users.nextcloud.extraGroups = [ "video" ];
			systemd.services.phpfpm-nextcloud.serviceConfig = {
			DeviceAllow = "/dev/dri/renderD128 rw";
			PrivateDevices = lib.mkForce false;
			};
			</syntaxhighlight>You will still need to enable the relevant app configuration through "Administration Settings > Memories > HW Acceleration".
	[[Category:Server]]		[[Category:Server]]
	[[Category:Applications]]		[[Category:Applications]]
	[[Category:Web Applications]]		[[Category:Web Applications]]
	[[Category:NixOS Manual]]		[[Category:NixOS Manual]]

Cameo007: Add config for public-facing whiteboard server

2026-04-22T21:54:59Z

Add config for public-facing whiteboard server

← Older revision		Revision as of 21:54, 22 April 2026
Line 490:		Line 490:

	=== Whiteboard ===		=== Whiteboard ===
	The [https://github.com/nextcloud/whiteboard Whiteboard app] requires a running backend server which is also packaged in NixOS.<syntaxhighlight lang="nix">		The [https://github.com/nextcloud/whiteboard Whiteboard app] requires a running backend server which is also packaged in NixOS.<syntaxhighlight lang="nix">environment.etc."nextcloud-whiteboard-secret".text = ''
	environment.etc."nextcloud-whiteboard-secret".text = ''
	JWT_SECRET_KEY=test123		JWT_SECRET_KEY=test123
	'';		'';
Line 500:		Line 499:
	secrets = [ /etc/nextcloud-whiteboard-secret ];		secrets = [ /etc/nextcloud-whiteboard-secret ];
	};		};
	</syntaxhighlight>After applying the configuration configure the Nextcloud app to use it<syntaxhighlight lang="bash">
	nextcloud-occ config:app:set whiteboard collabBackendUrl --value="http://localhost:3002"		# Expose whiteboard server in case you don’t operate your Nextcloud on localhost
	nextcloud-occ config:app:set whiteboard jwt_secret_key --value="test123"		services.nginx.virtualHosts.${config.services.nextcloud.hostName}.locations."/whiteboard/" = {
	</syntaxhighlight>		proxyPass = "http://localhost:3002/";
			proxyWebsockets = true;
			};</syntaxhighlight>After applying the configuration configure the Nextcloud app to use it<syntaxhighlight lang="bash">
			nextcloud-occ config:app:set whiteboard collabBackendUrl --value="http://localhost:3002" # localhost only
			nextcloud-occ config:app:set whiteboard collabBackendUrl --value="http://cloud.example.com/whiteboard" # Public (The domain is your Nextcloud hostname)
			nextcloud-occ config:app:set whiteboard jwt_secret_key --value="test123"</syntaxhighlight>

	=== NextCloud Office ===		=== NextCloud Office ===

KMalone42: In previous edit, I didn't add the markup filename + language header.

2026-01-31T18:12:24Z

In previous edit, I didn't add the markup filename + language header.

← Older revision		Revision as of 18:12, 31 January 2026
Line 15:		Line 15:
	config.dbtype = "sqlite";		config.dbtype = "sqlite";
	};		};
	</nowiki>\|name=\|lang=}}		</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}

	After that you will be able to login into your Nextcloud instance at <code><nowiki>http://localhost</nowiki></code> with user <code>root</code> and password <code>PWD</code> as configured above.		After that you will be able to login into your Nextcloud instance at <code><nowiki>http://localhost</nowiki></code> with user <code>root</code> and password <code>PWD</code> as configured above.

KMalone42: Added config.dbtype to minimal example. New minimal example conforms to 25.05+ standard configuration.

2026-01-31T18:05:32Z

Added config.dbtype to minimal example. New minimal example conforms to 25.05+ standard configuration.

← Older revision		Revision as of 18:05, 31 January 2026
Line 13:		Line 13:
	hostName = "localhost";		hostName = "localhost";
	config.adminpassFile = "/etc/nextcloud-admin-pass";		config.adminpassFile = "/etc/nextcloud-admin-pass";
			config.dbtype = "sqlite";
	};		};
	</nowiki>}}		</nowiki>\|name=\|lang=}}

	After that you will be able to login into your Nextcloud instance at <code><nowiki>http://localhost</nowiki></code> with user <code>root</code> and password <code>PWD</code> as configured above.		After that you will be able to login into your Nextcloud instance at <code><nowiki>http://localhost</nowiki></code> with user <code>root</code> and password <code>PWD</code> as configured above.

O5-J: Update NextCloud Objectstore Attribute Name

2026-01-27T16:50:39Z

Update NextCloud Objectstore Attribute Name

← Older revision		Revision as of 16:50, 27 January 2026
Line 127:		Line 127:
	In this example we'll configure a local S3-compatible object store using Minio and connect it to Nextcloud		In this example we'll configure a local S3-compatible object store using Minio and connect it to Nextcloud

	{{file\|~~/etc/nixos/configuration.nix~~\|~~nix~~\|<nowiki>		{{file\|\|\|<nowiki>
	{ ... } let		{ ... } let

Line 144:		Line 144:
	enable = true;		enable = true;
	bucket = "nextcloud";		bucket = "nextcloud";
	~~autocreate~~ = true;		verify_bucket_exists = true;
	key = accessKey;		key = accessKey;
	secretFile = "${pkgs.writeText "secret" "test12345"}";		secretFile = "${pkgs.writeText "secret" "test12345"}";
Line 165:		Line 165:

	};		};
	</nowiki>}}		</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}

	We'll need to run two commands to create the bucket <code>nextcloud</code> by using the access key <code>nextcloud</code> and the secret key <code>test12345</code>.		We'll need to run two commands to create the bucket <code>nextcloud</code> by using the access key <code>nextcloud</code> and the secret key <code>test12345</code>.

Arnecc: added link and explanation for two-factor authentication

2026-01-18T11:52:12Z

added link and explanation for two-factor authentication

← Older revision		Revision as of 11:52, 18 January 2026
Line 334:		Line 334:
	services.nginx.virtualHosts."${config.services.nextcloud.hostName}".listen = [ { addr = "127.0.0.1"; port = 8080; } ];		services.nginx.virtualHosts."${config.services.nextcloud.hostName}".listen = [ { addr = "127.0.0.1"; port = 8080; } ];
	</nowiki>}}		</nowiki>}}

			=== Enable Two-factor authentication ===

			Two-factor authentication can be enabled for your server via the administration interface in your browser. There is no way to declare this setting via nix configuration, so you should follow the [https://docs.nextcloud.com/server/latest/admin_manual/configuration_user/two_factor-auth.html official documentation] to set up Two-factor authentication.

	=== Enable HEIC image preview ===		=== Enable HEIC image preview ===

Onny: Redis caching is now enabled as default with NixOS 25.11

2025-11-27T12:33:40Z

Redis caching is now enabled as default with NixOS 25.11

@@ Line 114: / Line 114: @@
 };
 </nowiki>}}
 === Data storage ===

Raboof: /* Configuration */ backups

2025-10-24T14:50:40Z

Configuration: backups

← Older revision		Revision as of 14:50, 24 October 2025
Line 129:		Line 129:
	Note that APCu will still be used for local caching, as recommended by Nextcloud upstream.		Note that APCu will still be used for local caching, as recommended by Nextcloud upstream.

	=== ~~Object store~~ ===		=== Data storage ===
			Nextcloud stores metadata in the database and files either on a local filesystem, external storage, or in an object storage.

			==== Local filesystem ====
			Using a filesystem with snapshot support, such as btrfs or zfs, may be useful for backup purposes

			==== External storage ====
			https://docs.nextcloud.com/server/stable/admin_manual/configuration_files/external_storage_configuration_gui.html

			==== Object store ====
	In this example we'll configure a local S3-compatible object store using Minio and connect it to Nextcloud		In this example we'll configure a local S3-compatible object store using Minio and connect it to Nextcloud

Line 276:		Line 284:
	};		};
	</nowiki>}}		</nowiki>}}

			=== Backups ===
			You should make backups of both the database and your storage.

			For the database, [https://search.nixos.org/options?show=services.mysqlBackup services.mysqlBackup] or [https://search.nixos.org/options?show=services.postgresqlBackup services.postgresqlBackup] may come in handy. For local storage backups, periodically taking a snapshot of a snapshot-enabled filesystem such as btrfs or zfs may be a good first step. Remember to also make off-site copies.

	== Clients ==		== Clients ==

Raboof: formatting

2025-10-24T14:12:59Z

formatting

← Older revision		Revision as of 14:12, 24 October 2025
Line 266:		Line 266:
	** [https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/config_sample_php_parameters.html#passwordsalt passwordsalt]		** [https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/config_sample_php_parameters.html#passwordsalt passwordsalt]
	** [https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/config_sample_php_parameters.html#secret secret]		** [https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/config_sample_php_parameters.html#secret secret]
	* To be able to configure TLS for your new instance before you've updated your DNS record, you can use [[ACME#DNS challenge\|ACME DNS Challenge]]. Don't forget to clear <code>acmeRoot</code>:		* To be able to configure TLS for your new instance before you've updated your DNS record, you can use [[ACME#DNS challenge\|ACME DNS Challenge]]. Don't forget to clear <code>acmeRoot</code>:
	services.nginx.virtualHosts.${config.services.nextcloud.hostName} = {
	forceSSL = true;		{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>
	enableACME = true;		services.nginx.virtualHosts.${config.services.nextcloud.hostName} = {
	# force DNS-01 validation		forceSSL = true;
	acmeRoot = null;		enableACME = true;
	};		# force DNS-01 validation
			acmeRoot = null;
			};
			</nowiki>}}

	== Clients ==		== Clients ==

Raboof: /* Migration */ example code for clearing acmeRoot

2025-10-24T14:11:59Z

Migration: example code for clearing acmeRoot

← Older revision		Revision as of 14:11, 24 October 2025
Line 266:		Line 266:
	** [https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/config_sample_php_parameters.html#passwordsalt passwordsalt]		** [https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/config_sample_php_parameters.html#passwordsalt passwordsalt]
	** [https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/config_sample_php_parameters.html#secret secret]		** [https://docs.nextcloud.com/server/stable/admin_manual/configuration_server/config_sample_php_parameters.html#secret secret]
	* To be able to configure TLS for your new instance before you've updated your DNS record, you can use [[ACME#DNS challenge\|ACME DNS Challenge]].		* To be able to configure TLS for your new instance before you've updated your DNS record, you can use [[ACME#DNS challenge\|ACME DNS Challenge]]. Don't forget to clear <code>acmeRoot</code>:
			services.nginx.virtualHosts.${config.services.nextcloud.hostName} = {
			forceSSL = true;
			enableACME = true;
			# force DNS-01 validation
			acmeRoot = null;
			};

	== Clients ==		== Clients ==