2023-12-24 07:50:22 +01:00
|
|
|
# Nextcloud Server Service {#services-nextcloud-server}
|
|
|
|
|
|
|
|
Defined in [`/modules/services/nextcloud-server.nix`](@REPO@/modules/services/nextcloud-server.nix).
|
|
|
|
|
|
|
|
This NixOS module is a service that sets up a [Nextcloud Server](https://nextcloud.com/).
|
|
|
|
|
|
|
|
## Features {#services-nextcloud-server-features}
|
|
|
|
|
2024-01-06 09:03:56 +01:00
|
|
|
- Declarative [Apps](#services-nextcloud-server-options-shb.nextcloud.apps) Configuration - no need
|
|
|
|
to configure those with the UI.
|
2024-01-06 18:43:30 +01:00
|
|
|
- [LDAP](#services-nextcloud-server-usage-ldap) app: enables app and sets up integration with an existing LDAP server.
|
2024-01-22 08:38:57 +01:00
|
|
|
- [OIDC](#services-nextcloud-server-usage-oidc) app: enables app and sets up integration with an existing OIDC server.
|
2024-01-06 18:43:30 +01:00
|
|
|
- [Preview Generator](#services-nextcloud-server-usage-previewgenerator) app: enables app and sets
|
2024-01-06 00:26:56 +01:00
|
|
|
up required cron job.
|
2024-01-06 18:43:30 +01:00
|
|
|
- [Only Office](#services-nextcloud-server-usage-onlyoffice) app: enables app and sets up Only
|
2024-01-06 00:26:32 +01:00
|
|
|
Office service.
|
2024-01-06 09:03:56 +01:00
|
|
|
- Any other app through the
|
|
|
|
[shb.nextcloud.extraApps](#services-nextcloud-server-options-shb.nextcloud.extraApps) option.
|
2023-12-24 07:50:22 +01:00
|
|
|
- [Demo](./demo-nextcloud-server.html)
|
2023-12-30 18:51:55 +01:00
|
|
|
- Demo deploying a Nextcloud server with [Colmena](https://colmena.cli.rs/) and with proper
|
|
|
|
secrets management with [sops-nix](https://github.com/Mic92/sops-nix).
|
2023-12-24 07:50:22 +01:00
|
|
|
- Access through subdomain using reverse proxy.
|
|
|
|
- Access through HTTPS using reverse proxy.
|
|
|
|
- Automatic setup of PostgreSQL database.
|
2024-01-06 00:26:32 +01:00
|
|
|
- Automatic setup of Redis database for caching.
|
2023-12-24 07:50:22 +01:00
|
|
|
- Backup of the [`shb.nextcloud.dataDir`][1] through the [backup block](./blocks-backup.html).
|
|
|
|
- Monitoring of reverse proxy, PHP-FPM, and database backups through the [monitoring
|
|
|
|
block](./blocks-monitoring.html).
|
2024-01-06 00:26:32 +01:00
|
|
|
- [Integration Tests](@REPO@/test/vm/nextcloud.nix)
|
|
|
|
- Tests system cron job is setup correctly.
|
|
|
|
- Tests initial admin user and password are setup correctly.
|
|
|
|
- Tests admin user can create and retrieve a file through WebDAV.
|
2023-12-24 07:50:22 +01:00
|
|
|
- Access to advanced options not exposed here thanks to how NixOS modules work.
|
|
|
|
|
|
|
|
[1]: ./services-nextcloud.html#services-nextcloud-server-options-shb.nextcloud.dataDir
|
|
|
|
|
|
|
|
## Usage {#services-nextcloud-server-usage}
|
|
|
|
|
2024-01-22 08:38:57 +01:00
|
|
|
### Secrets {#services-nextcloud-server-secrets}
|
2024-01-06 18:43:30 +01:00
|
|
|
|
2024-01-22 08:38:57 +01:00
|
|
|
All the secrets should be readable by the nextcloud user.
|
|
|
|
|
|
|
|
Secret should not be stored in the nix store. If you're using
|
|
|
|
[sops-nix](https://github.com/Mic92/sops-nix) and assuming your secrets file is located at
|
|
|
|
`./secrets.yaml`, you can define a secret with:
|
|
|
|
|
|
|
|
```nix
|
|
|
|
sops.secrets."nextcloud/adminpass" = {
|
|
|
|
sopsFile = ./secrets.yaml;
|
|
|
|
mode = "0400";
|
|
|
|
owner = "nextcloud";
|
|
|
|
group = "nextcloud";
|
|
|
|
restartUnits = [ "phpfpm-nextcloud.service" ];
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
|
|
|
Then you can use that secret:
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.nextcloud.adminPassFile = config.sops.secrets."nextcloud/adminpass".path;
|
|
|
|
```
|
|
|
|
|
|
|
|
### Nextcloud through HTTP {#services-nextcloud-server-usage-basic}
|
|
|
|
|
|
|
|
:::: {.note}
|
|
|
|
This section corresponds to the `basic` section of the [Nextcloud
|
|
|
|
demo](demo-nextcloud-server.html#demo-nextcloud-deploy-basic).
|
|
|
|
::::
|
2023-12-24 07:50:22 +01:00
|
|
|
|
|
|
|
This will set up a Nextcloud service that runs on the NixOS target machine, reachable at
|
|
|
|
`http://nextcloud.example.com`. If the `shb.ssl` block is [enabled](block-ssl.html#usage), the
|
|
|
|
instance will be reachable at `https://nextcloud.example.com`.
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.nextcloud = {
|
|
|
|
enable = true;
|
|
|
|
domain = "example.com";
|
|
|
|
subdomain = "nextcloud";
|
|
|
|
dataDir = "/var/lib/nextcloud";
|
|
|
|
adminPassFile = <path/to/secret>;
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
2024-01-22 08:38:57 +01:00
|
|
|
After deploying, the Nextcloud server will be reachable at `http://nextcloud.example.com`.
|
2023-12-24 07:50:22 +01:00
|
|
|
|
2024-01-06 18:43:30 +01:00
|
|
|
### With LDAP Support {#services-nextcloud-server-usage-ldap}
|
|
|
|
|
2024-01-22 08:38:57 +01:00
|
|
|
:::: {.note}
|
|
|
|
This section corresponds to the `ldap` section of the [Nextcloud
|
|
|
|
demo](demo-nextcloud-server.html#demo-nextcloud-deploy-ldap).
|
|
|
|
::::
|
2024-01-06 18:43:30 +01:00
|
|
|
|
2024-01-22 08:38:57 +01:00
|
|
|
We will build upon the [Basic Configuration](#services-nextcloud-server-usage-basic) section, so
|
|
|
|
please read that first.
|
|
|
|
|
|
|
|
We will use the LDAP block provided by Self Host Blocks to setup a
|
2024-01-06 18:43:30 +01:00
|
|
|
[LLDAP](https://github.com/lldap/lldap) service.
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.ldap = {
|
|
|
|
enable = true;
|
|
|
|
domain = "example.com";
|
|
|
|
subdomain = "ldap";
|
|
|
|
ldapPort = 3890;
|
|
|
|
webUIListenPort = 17170;
|
|
|
|
dcdomain = "dc=example,dc=com";
|
2024-01-22 08:38:57 +01:00
|
|
|
ldapUserPasswordFile = <path/to/ldapUserPasswordSecret>;
|
|
|
|
jwtSecretFile = <path/to/ldapJwtSecret>;
|
2024-01-06 18:43:30 +01:00
|
|
|
};
|
|
|
|
```
|
|
|
|
|
|
|
|
We also need to configure the `nextcloud` Self Host Blocks service to talk to the LDAP server we
|
|
|
|
just defined:
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.nextcloud.apps.ldap
|
|
|
|
enable = true;
|
|
|
|
host = "127.0.0.1";
|
|
|
|
port = config.shb.ldap.ldapPort;
|
|
|
|
dcdomain = config.shb.ldap.dcdomain;
|
|
|
|
adminName = "admin";
|
2024-01-22 08:38:57 +01:00
|
|
|
adminPasswordFile = <path/to/ldapUserPasswordSecret>;
|
2024-01-06 18:43:30 +01:00
|
|
|
userGroup = "nextcloud_user";
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
2024-01-22 08:38:57 +01:00
|
|
|
The `shb.nextcloud.apps.ldap.adminPasswordFile` must be the same as the
|
|
|
|
`shb.ldap.ldapUserPasswordFile`. The other secret can be randomly generated with `nix run
|
|
|
|
nixpkgs#openssl -- rand -hex 64`.
|
|
|
|
|
|
|
|
And that's it. Now, go to the LDAP server at `http://ldap.example.com`, create the `nextcloud_user`
|
|
|
|
group, create a user and add it to the group. When that's done, go back to the Nextcloud server at
|
|
|
|
`http://nextcloud.example.com` and login with that user.
|
|
|
|
|
|
|
|
Note that we cannot create an admin user from the LDAP server, so you need to create a normal user
|
|
|
|
like above, login with it once so it is known to Nextcloud, then logout, login with the admin
|
|
|
|
Nextcloud user and promote that new user to admin level.
|
|
|
|
|
|
|
|
### With OIDC Support {#services-nextcloud-server-usage-oidc}
|
|
|
|
|
|
|
|
:::: {.note}
|
|
|
|
This section corresponds to the `sso` section of the [Nextcloud
|
|
|
|
demo](demo-nextcloud-server.html#demo-nextcloud-deploy-sso).
|
|
|
|
::::
|
|
|
|
|
|
|
|
We will build upon the [Basic Configuration](#services-nextcloud-server-usage-basic) and [With LDAP
|
|
|
|
Support](#services-nextcloud-server-usage-ldap) sections, so please read those first and setup the
|
|
|
|
LDAP app as described above.
|
|
|
|
|
|
|
|
Here though, we must setup SSL certificates because the SSO provider only works with the https
|
|
|
|
protocol. This is actually quite easy thanks to the [SSL block](blocks-ssl.html). For example, with
|
|
|
|
self-signed certificates:
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.certs = {
|
|
|
|
cas.selfsigned.myca = {
|
|
|
|
name = "My CA";
|
|
|
|
};
|
|
|
|
certs.selfsigned = {
|
|
|
|
nextcloud = {
|
|
|
|
ca = config.shb.certs.cas.selfsigned.myca;
|
|
|
|
domain = "nextcloud.example.com";
|
|
|
|
};
|
|
|
|
auth = {
|
|
|
|
ca = config.shb.certs.cas.selfsigned.myca;
|
|
|
|
domain = "auth.example.com";
|
|
|
|
};
|
|
|
|
ldap = {
|
|
|
|
ca = config.shb.certs.cas.selfsigned.myca;
|
|
|
|
domain = "ldap.example.com";
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
|
|
|
We need to setup the SSO provider, here Authelia thanks to the corresponding SHB block:
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.authelia = {
|
|
|
|
enable = true;
|
|
|
|
domain = "example.com";
|
|
|
|
subdomain = "auth";
|
|
|
|
ssl = config.shb.certs.certs.selfsigned.auth;
|
|
|
|
|
|
|
|
ldapEndpoint = "ldap://127.0.0.1:${builtins.toString config.shb.ldap.ldapPort}";
|
|
|
|
dcdomain = config.shb.ldap.dcdomain;
|
|
|
|
|
|
|
|
secrets = {
|
|
|
|
jwtSecretFile = <path/to/autheliaJwtSecret>;
|
|
|
|
ldapAdminPasswordFile = <path/to/ldapUserPasswordSecret>;
|
|
|
|
sessionSecretFile = <path/to/autheliaSessionSecret>;
|
|
|
|
storageEncryptionKeyFile = <path/to/autheliaStorageEncryptionKeySecret>;
|
|
|
|
identityProvidersOIDCHMACSecretFile = <path/to/providersOIDCHMACSecret>;
|
|
|
|
identityProvidersOIDCIssuerPrivateKeyFile = <path/to/providersOIDCIssuerSecret>;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
|
|
|
The `shb.authelia.secrets.ldapAdminPasswordFile` must be the same as the
|
|
|
|
`shb.ldap.ldapUserPasswordFile` defined in the previous section. The secrets can be randomly
|
|
|
|
generated with `nix run nixpkgs#openssl -- rand -hex 64`.
|
|
|
|
|
|
|
|
Now, on the Nextcloud side, you need to add the following options:
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.nextcloud.ssl = config.shb.certs.certs.selfsigned.nextcloud;
|
|
|
|
|
|
|
|
shb.nextcloud.apps.sso = {
|
|
|
|
enable = true;
|
|
|
|
endpoint = "https://${config.shb.authelia.subdomain}.${config.shb.authelia.domain}";
|
|
|
|
clientID = "nextcloud";
|
|
|
|
fallbackDefaultAuth = false;
|
|
|
|
|
|
|
|
secretFile = <path/to/oidcNextcloudSharedSecret>;
|
|
|
|
secretFileForAuthelia = <path/to/oidcNextcloudSharedSecret>;
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
|
|
|
Passing the `ssl` option will auto-configure nginx to force SSL connections with the given
|
|
|
|
certificate.
|
|
|
|
|
|
|
|
The `shb.nextcloud.apps.sso.secretFile` and `shb.nextcloud.apps.sso.secretFileForAuthelia` options
|
|
|
|
must have the same content. The former is a file that must be owned by the `nextcloud` user while
|
|
|
|
the latter must be owned by the `authelia` user. I want to avoid needing to define the same secret
|
|
|
|
twice with a future secrets SHB block.
|
2024-01-06 18:43:30 +01:00
|
|
|
|
2023-12-24 07:50:22 +01:00
|
|
|
### Tweak PHPFpm Config {#services-nextcloud-server-usage-phpfpm}
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.nextcloud.phpFpmPoolSettings = {
|
|
|
|
"pm" = "dynamic";
|
|
|
|
"pm.max_children" = 800;
|
|
|
|
"pm.start_servers" = 300;
|
|
|
|
"pm.min_spare_servers" = 300;
|
|
|
|
"pm.max_spare_servers" = 500;
|
|
|
|
"pm.max_spawn_rate" = 50;
|
|
|
|
"pm.max_requests" = 50;
|
|
|
|
"pm.process_idle_timeout" = "20s";
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
|
|
|
### Tweak PostgreSQL Settings {#services-nextcloud-server-usage-postgres}
|
|
|
|
|
2024-01-22 08:38:57 +01:00
|
|
|
These settings will impact all databases.
|
|
|
|
|
2023-12-24 07:50:22 +01:00
|
|
|
```nix
|
|
|
|
shb.nextcloud.postgresSettings = {
|
|
|
|
max_connections = "100";
|
|
|
|
shared_buffers = "512MB";
|
|
|
|
effective_cache_size = "1536MB";
|
|
|
|
maintenance_work_mem = "128MB";
|
|
|
|
checkpoint_completion_target = "0.9";
|
|
|
|
wal_buffers = "16MB";
|
|
|
|
default_statistics_target = "100";
|
|
|
|
random_page_cost = "1.1";
|
|
|
|
effective_io_concurrency = "200";
|
|
|
|
work_mem = "2621kB";
|
|
|
|
huge_pages = "off";
|
|
|
|
min_wal_size = "1GB";
|
|
|
|
max_wal_size = "4GB";
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
|
|
|
### Backup the Nextcloud data {#services-nextcloud-server-usage-backup}
|
|
|
|
|
|
|
|
TODO
|
|
|
|
|
2024-01-06 18:43:30 +01:00
|
|
|
### Enable Preview Generator App {#services-nextcloud-server-usage-previewgenerator}
|
|
|
|
|
|
|
|
The following snippet installs and enables the [Preview
|
|
|
|
Generator](https://apps.nextcloud.com/apps/previewgenerator) application as well as creates the
|
|
|
|
required cron job that generates previews every 10 minutes.
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.nextcloud.apps.previewgenerator.enable = true;
|
|
|
|
```
|
|
|
|
|
|
|
|
Note that you still need to generate the previews for any pre-existing files with:
|
|
|
|
|
|
|
|
```bash
|
|
|
|
nextcloud-occ -vvv preview:generate-all
|
|
|
|
```
|
|
|
|
|
|
|
|
### Enable OnlyOffice App {#services-nextcloud-server-usage-onlyoffice}
|
2023-12-24 07:50:22 +01:00
|
|
|
|
2024-01-06 18:43:30 +01:00
|
|
|
The following snippet installs and enables the [Only
|
|
|
|
Office](https://apps.nextcloud.com/apps/onlyoffice) application as well as sets up an Only Office
|
|
|
|
instance listening at `onlyoffice.example.com` that only listens on the local network.
|
2023-12-24 07:50:22 +01:00
|
|
|
|
|
|
|
```nix
|
2024-01-06 18:43:30 +01:00
|
|
|
shb.nextcloud.apps.onlyoffice = {
|
|
|
|
enable = true;
|
2023-12-24 07:50:22 +01:00
|
|
|
subdomain = "onlyoffice";
|
|
|
|
localNextworkIPRange = "192.168.1.1/24";
|
|
|
|
};
|
|
|
|
```
|
|
|
|
|
|
|
|
Also, you will need to explicitly allow the package `corefonts`:
|
|
|
|
|
|
|
|
```nix
|
|
|
|
nixpkgs.config.allowUnfreePredicate = pkg: builtins.elem (pkgs.lib.getName pkg) [
|
|
|
|
"corefonts"
|
|
|
|
];
|
|
|
|
```
|
|
|
|
|
|
|
|
### Enable Monitoring {#services-nextcloud-server-server-usage-monitoring}
|
|
|
|
|
2024-01-06 18:43:30 +01:00
|
|
|
Enable the [monitoring block](./blocks-monitoring.html). The metrics will automatically appear in
|
|
|
|
the corresponding dashboards.
|
2023-12-24 07:50:22 +01:00
|
|
|
|
|
|
|
### Enable Tracing {#services-nextcloud-server-server-usage-tracing}
|
|
|
|
|
|
|
|
You can enable tracing with:
|
|
|
|
|
|
|
|
```nix
|
|
|
|
shb.nextcloud.debug = true;
|
|
|
|
```
|
|
|
|
|
|
|
|
Traces will be located at `/var/log/xdebug`.
|
|
|
|
|
|
|
|
See [my blog
|
|
|
|
post](http://blog.tiserbox.com/posts/2023-08-12-what%27s-up-with-nextcloud-webdav-slowness.html) for
|
|
|
|
how to look at the traces.
|
|
|
|
|
|
|
|
## Demo {#services-nextcloud-server-demo}
|
|
|
|
|
2024-01-06 18:43:30 +01:00
|
|
|
Head over to the [Nextcloud demo](demo-nextcloud-server.html) for a demo that installs Nextcloud with or
|
|
|
|
without LDAP integration on a VM with minimal manual steps.
|
2023-12-24 07:50:22 +01:00
|
|
|
|
|
|
|
## Maintenance {#services-nextcloud-server-maintenance}
|
|
|
|
|
|
|
|
On the command line, the `occ` tool is called `nextcloud-occ`.
|
|
|
|
|
2024-01-22 08:38:57 +01:00
|
|
|
## Debug {#services-nextcloud-server-debug}
|
|
|
|
|
|
|
|
In case of an issue, check the logs for any systemd service mentioned in this section.
|
|
|
|
|
|
|
|
On startup, the oneshot systemd service `nextcloud-setup.service` starts. After it finishes, the
|
|
|
|
`phpfpm-nextcloud.service` starts to serve Nextcloud. The `nginx.service` is used as the reverse
|
|
|
|
proxy. `postgresql.service` run the database.
|
|
|
|
|
|
|
|
Nextcloud' configuration is found at `${shb.nextcloud.dataDir}/config/config.php`. Nginx'
|
|
|
|
configuration can be found with `systemctl cat nginx | grep -om 1 -e "[^ ]\+conf"`.
|
|
|
|
|
|
|
|
Enable verbose logging by setting the `shb.nextcloud.debug` boolean to `true`.
|
|
|
|
|
2024-01-29 07:33:49 +01:00
|
|
|
Access the database with `sudo -u nextcloud psql`.
|
|
|
|
|
|
|
|
Access Redis with `sudo -u nextcloud redis-cli -s /run/redis-nextcloud/redis.sock`.
|
|
|
|
|
2023-12-24 07:50:22 +01:00
|
|
|
## Options Reference {#services-nextcloud-server-options}
|
|
|
|
|
|
|
|
```{=include=} options
|
|
|
|
id-prefix: services-nextcloud-server-options-
|
|
|
|
list-id: selfhostblocks-service-nextcloud-options
|
|
|
|
source: @OPTIONS_JSON@
|
|
|
|
```
|