42.2 + Nextcloud 11 (step by step)

Hi there, Installing Nextcloud is easy, doing so in a decent configuration so you have a working product is not. Looking for some useful tips to given questions, and any others whose absence exposes a hole in my understanding of the problem: 1. Leap install - I’m creating a web-server, so presumably i want to max out the size of the /srv partition? 2. Which PHP - I understand 42.2 comes with 5.5 and 7.0, which is the default and how do i make sure i use 7.0? 3. Mariadb - I want this rather than SQLite, obviously, do i need to configure Mariadb before or after I do first setup on Nextcloud? 4. Apache https - Easiest method to do letsencrypt, and before or after first setup on Nextcloud? 5. What else have i missed? Many thanks

I would recommend docker containers for this but that may be too hard. Nevertheless, once you have your setup up and running, read up on docker and try to containerize it. Anyway, regarding your questions:

  1. use lvm. Partitioning is a waste of space. And nextcloud’s data dir does not have to be in the document root. You can set it to any directory as long as wwwrun user has access to it. I think it is even recommended to not have it in document root
  2. can’t say, I still have nextcloud 10 running on php5, I am lazy and waiting for an rpm to pop up in server:php:applications repo
  3. as with most web applications, you have to create the database and the user beforehand
  4. letsencrypt does not care about the web application. It just requires that whatever domain name you request a cert for resolves to the ip where the letsencrypt client runs. I use letsencrypt in standalone mode, meaning I have to take down apache for a few seconds to run letsencrypt client

Depending on the scope of your install, you might want to put some basic security and defense mechanisms in place. Like firewalls, intrusion detection, geoip deny, blacklisting and such.

An SDB has been created for Nextcloud and looks to have been updated to running on 42.2.

https://en.opensuse.org/SDB:Nextcloud

If you follow those instructions and run into a problem, post again…

TSU

thank you both.

i take it that mkdir /mnt/nextcloud_data is only used as an examples, as it sits on root which is the small ‘system’ partition, only 12gb in size on my laptop. on a standard install it is the home partition that ends up taking up most of the driver, so i guess somewhere in there would be more appropriate? the guide does not appear to cover enabling apache to use a self-signed cert (as I don’t have a domain that would allow me to use letsencrypt), is there a good link that deals with this, and advice on where to slipstream this process in the nextcloud SDB process? thanks

File and directory ownership and permissions are important. More so then the exact path used.

When you first install openSUSE (any version) and intend to use the machine almost always as a Server,

I highly recommend not created the separate /home partition for Users, or modify the layout to minimize the size of that partiton.
By doing so, you will maximize the space automatically allocated to the root partiton (Assume you’re still using the auto partitioner during installation), but check the result, and by default all Server applications will install into, and locate their data in the root partition.

TSU

You can use the suse repos:

Nextcloud-Server: https://software.opensuse.org/ymp/server:php:applications/openSUSE_Leap_42.2/nextcloud.ymp?base=openSUSE%3ALeap%3A42.2&query=nextcloud
Nextcloud-Client: https://software.opensuse.org/ymp/openSUSE:Leap:42.2/standard/nextcloud-client.ymp?base=openSUSE%3ALeap%3A42.2&query=nextcloud-client

And for letsencrypt use certbot:
https://software.opensuse.org/ymp/devel:languages:python/openSUSE_Leap_42.2/certbot.ymp?base=openSUSE%3ALeap%3A42.2&query=certbot

PS: request for nextcloud 11 is startet for some days.