mother-of-all-self-hosting / ansible-role-nextcloud

An Ansible role for installing the Nextcloud groupware server

Nextcloud Ansible role

This is an Ansible role which installs Nextcloud to run as a Docker container wrapped in a systemd service.

This role implicitly depends on:

• com.devture.ansible.role.playbook_help
• com.devture.ansible.role.systemd_docker_base

Check defaults/main.yml for the full list of supported options.

For an Ansible playbook which integrates this role and makes it easier to use, see the mash-playbook.

ansible-role-nextcloud's Issues

`nextcloud_base_path` expansion

Hi. I'm trying to install a second nextcloud instance within my mash-server, using a second playbook with a different nextcloud_identifier. However I'm wondering if I got the idea wrong, because the installation path of nextcloud is not being adapted.

Here it says

nextcloud_base_path: "{{ nextcloud_base_path }}/nextcloud"

where intuitively I'd expect

nextcloud_base_path: "{{ nextcloud_identifier }}/"

or maybe installing a second nextcloud actually needs a second mash-instance...?

/entrypoint.sh: 78: cannot create /usr/local/etc/php/conf.d/redis-session.ini: Read-only file system

With basic install my mash-nextcloud-server log says this:

/entrypoint.sh: 78: cannot create /usr/local/etc/php/conf.d/redis-session.ini: Read-only file system

It seems that nextcloud/docker#763 (comment) solves that issue. As I have other troubles I am not 100% sure it does fixes the problem always and does not introduce other issues. Also I wasn't sure how to check if redis is used, or where to put the redis-session file, so I opened this issue here.

incorrect folder link re: {{ nextcloud_container_labels_additional_labels }} in comment

i created a pull request correcting the mistake (i believe). is this the best way to address minor corrections like this?

Why bind the `data` directory the `/var/www/html`?

Currently, this creates a bind point for the data directory to the /var/www/html directory within the container

ansible-role-nextcloud/templates/systemd/server.service.j2

Line 30 in 7484539

--mount type=bind,src={{ nextcloud_data_path }},dst=/var/www/html \

Wouldn't we want to use the nextcloud_base_path instead? Shouldn't the data directory be mounted at /var/www/html/data point within the container?

Currently I have a folder for Nextcloud data on NFS. When I provided this role the /mnt/nas data directory in the variable nextcloud_data_path, the Nextcloud container wasn't able to run. However, when I set this line:

ansible-role-nextcloud/templates/systemd/server.service.j2

Line 30 in 7484539

--mount type=bind,src={{ nextcloud_data_path }},dst=/var/www/html \

To

--mount type=bind,src={{ nextcloud_base_path }},dst=/var/www/html

It at least ran, but wasn't able to find any configuration files...