1:39 p.m.
Hi Maciej,
already the next question. While playing around with an own nextcloud
ansible role, I realized the debops.owncloud role does manage an
nextcloud instance already for a while.
As long as I understand it just configure one owncloud/nextcloud
instance for one server.
Do you think it's possible to extend the role for multiple nextcloud
instances with different databases and webroot (maybe php-pools) and if
yes: could you point me to an good starting point how to achieve that?
Maybe it's better to add a new role like owncloud-instances which refer
to debops.owncloud.
Any advise?
Thanks and kind regards!
Jan
3:27 p.m.
On Jan 29, Jan Kowalsky wrote:
already the next question. While playing around with an own
nextcloud
ansible role, I realized the debops.owncloud role does manage an
nextcloud instance already for a while.
As long as I understand it just configure one owncloud/nextcloud
instance for one server.
Do you think it's possible to extend the role for multiple nextcloud
instances with different databases and webroot (maybe php-pools) and if
yes: could you point me to an good starting point how to achieve that?
Maybe it's better to add a new role like owncloud-instances which refer
to debops.owncloud.
I don't think that reworking current 'debops.owncloud' role to support
multiple instances is workable. It currently supports both ownCloud and
Nextcloud, one with .deb packages, the second with tarballs, extending this to
multiple instances would probably make things unreadable.
I would try and create a new 'debops.nextcloud' role and try to support
multiple instances of Nextcloud from scratch. If it's too difficult, there's
also an option of creating an LXC container for each instance and putting
a nginx proxy in front of all of them. It can be later extended to separate
hosts for each instance if need be.
Cheers,
Maciej
12:48 p.m.
Am 29.01.19 um 15:27 schrieb Maciej Delmanowski:
If it's too difficult, there's also an option of creating an
LXC
container for each instance and putting a nginx proxy in front of
all of them. It can be later extended to separate hosts for each
instance if need be.
I don't want to talk you out of using debops here ;-) but I suggest
to talk a look at running nextcloud within a docker container. They
provide official images:
https://github.com/nextcloud/docker
You can set up the docker host via debops.docker:
https://docs.debops.org/en/latest/ansible/roles/debops.docker/
and even define the containers via ansible (afaik debops doesn't yet
support that?):
https://docs.ansible.com/ansible/latest/modules/docker_container_module.html
For sure a reverse proxy in front of the containers is needed here.
nginx or haproxy or traefik ...
btw: I already run such a setup ... ok, one nc-instance only, but
anyway working fine.
Stefan
1:56 p.m.
On Jan 30, Stefan G. Weichinger wrote:
You can set up the docker host via debops.docker:
https://docs.debops.org/en/latest/ansible/roles/debops.docker/
and even define the containers via ansible (afaik debops doesn't yet
support that?):
https://docs.ansible.com/ansible/latest/modules/docker_container_module.html
You can define the containers in a custom playbook, either directly as Docker
images, or as a docker-compose setup. The playbook needs to use a custom
Ansible Python interpreter that lives in the Docker Python virtualenv set up
by the 'debops.docker' role. It's explained in the 'debops.docker'
documentation.
Maciej
2152
days inactive
2153
days old
3 comments
3 participants
participants (3)
-
Jan Kowalsky -
Maciej Delmanowski -
Stefan G. Weichinger