Changes

From SME Server
Jump to navigationJump to search

Nextcloud (view source)

Revision as of 19:37, 1 December 2020

3,647 bytes added ,  19:37, 1 December 2020
no edit summary
Line 155: Line 155:  
=== Uninstall ===
 
=== Uninstall ===
 
  yum remove {{#var:smecontribname}}  {{#var:contribname}}
 
  yum remove {{#var:smecontribname}}  {{#var:contribname}}
 +
 +
=== Use a dedicated domain to connect to Nextcloud ===
 +
<syntaxhighlight lang="bash">
 +
db domains set cloud.mydomain.com domain Description "Nextcloud" Content Primary Nameservers internet TemplatePath WebAppVirtualHost DocumentRoot /usr/share/nextcloud RequireSSL enabled letsencryptSSLcert enabled
 +
signal-event domain-create cloud.mydomain.com
 +
 +
#this one to let nextcloud DAV be redirect correctly
 +
config setprop nextcloud CloudDomain cloud.mydomain.com
 +
signal-event nextcloud-update
 +
 +
#only if you use a Let's Encrypt certificate
 +
expand-template /etc/dehydrated/domains.txt
 +
dehydrated -c
 +
 +
</syntaxhighlight>
 +
 +
=== Move user space from uuid to username ===
 +
User stored using ldap from SME with initial install will create a space with their ldap uuid. This is not very user friendly and further more it will lead to ios app issues.
 +
Recent version will use the username for new users, but for those already created you will need to do the following
 +
you will need to do as admin :
 +
# go to preference
 +
# choose ldap
 +
# choose expert
 +
# fill the 3 fields as presented above, or using the cli do
 +
  OCC ldap:set-config s01 ldapExpertUUIDGroupAttr cn
 +
  OCC ldap:set-config s01 ldapExpertUUIDUserAttr uid
 +
  OCC ldap:set-config s01 ldapExpertUsernameAttr uid
 +
# in cli, you will then need to do :
 +
  OCC user:list and save the content
 +
  cd /home/e-smith/files/nextcloud/data ; mv OLDUUID username
 +
  OCC files:scan username
 +
# delete the UUID association for users
 +
# you should then be able to login as the user with its previous files
 +
 +
Only drawback, trash history might be gone, a trick inside the db using a script could workaround that and avoid the OCC files:scan username
    
=== Mount with davfs on Fedora Clients ===
 
=== Mount with davfs on Fedora Clients ===
Line 176: Line 211:  
echo "https://example.com/nextcloud/remote.php/webdav your_Nextcloud_username your_password" >> ~/.davfs2/secrets  
 
echo "https://example.com/nextcloud/remote.php/webdav your_Nextcloud_username your_password" >> ~/.davfs2/secrets  
 
chmod 0600 ~/.davfs2/secrets
 
chmod 0600 ~/.davfs2/secrets
−
</syntaxhighlight>then just mount ! you should see the folder mount at every logon from now on, if you do not want that, change "auto in the fstab by noauto.<syntaxhighlight lang="bash">
+
</syntaxhighlight>then just mount ! <syntaxhighlight lang="bash">
 
mount ~/nextcloud
 
mount ~/nextcloud
 
</syntaxhighlight>
 
</syntaxhighlight>
   −
adapted from those sources:
+
From there you can tweak the cache configuration to make it easier for you if you are far from the server, default cache size is 50MiByte, you could increase it to let's say 3 GiByte in ~/.davfs2/davfs2.conf for your user <syntaxhighlight lang="bash">
 +
cache_size 3G
 +
</syntaxhighlight>you should see the folder mount at every logon from now on!  if you do not want that, change "auto" in the fstab by "noauto".
 +
 
 +
Then add the following in ~/bash_profile or ~/bash_rc. You could user also mount -a and to try to put something in /etc/gdm/PostLogin/" instead<syntaxhighlight lang="bash">
 +
mount /home/username/nextcloud
 +
 
 +
 
 +
 
 +
</syntaxhighlight>And Finally to umount in  gdm using "sudo vim /etc/gdm/PostSession/"<syntaxhighlight lang="bash">
 +
if [ ${USERNAME} = "myuser" ];then
 +
  umount -fl /home/myuser/nextcloud
 +
fi
 +
</syntaxhighlight>
 +
 
 +
Adapted from those sources:
 
* http://www.tuxfixer.com/mount-webdav-remote-storage-in-fedora-linux-via-davfs2/
 
* http://www.tuxfixer.com/mount-webdav-remote-storage-in-fedora-linux-via-davfs2/
 
* https://docs.nextcloud.com/server/13/user_manual/files/access_webdav.html
 
* https://docs.nextcloud.com/server/13/user_manual/files/access_webdav.html
Line 215: Line 265:     
repeat above for each major update until you are one update from the latest major update. At that point you can follow the usual process. source (https://bugs.contribs.org/show_bug.cgi?id=10670#c3)
 
repeat above for each major update until you are one update from the latest major update. At that point you can follow the usual process. source (https://bugs.contribs.org/show_bug.cgi?id=10670#c3)
 +
 +
==== Upgrading from 17.0.1.x to 17.07.x ====
 +
 +
You can use the built in updater.
 +
The only issue experienced was right at the end of the process with a http 500 error. I just did 'retry' and it completed.
 +
 +
You may need to update your database which I did as follows - note it may take a very long time with a lot of files:
 +
 +
OCC maintenance:mode --on
 +
OCC db:convert-filecache-bigint
 +
OCC maintenance:mode --off
 +
 +
==== User cannot see shares/files ====
 +
 +
After a new install the admin user could see shares but not a user.
 +
 +
We had a single ibay and it was set:
 +
 +
Group Everyone
 +
Write group
 +
Read everyone
 +
 +
We created a new group called localusers and added the admin and single user.
 +
 +
We then set the ibay:
 +
 +
Group localusers
 +
Write group
 +
Read group
 +
 +
This appeared to fix the issue and the user could now see the files.
 +
 +
====Reset Database====
 +
 +
For reference, whilst looking at resetting file caches I found this.
 +
 +
It is probably extremely dangerous but wanted to make a note.
 +
 +
https://github.com/nextcloud/server/issues/8113#issuecomment-565876798
 +
 +
===Koozali SMEv10 testing===
 +
 +
We are still building Koozali SME v10 and have been testing installation of Nextcloud, currently on version 20.
 +
 +
We have packages in smedev.
 +
 +
You will also need packages from some other repos.
 +
    
=== Bugs ===
 
=== Bugs ===
Retrieved from "https://wiki.koozali.org/Special:MobileDiff/38118...39029"

Navigation menu