Changes

From SME Server
Jump to navigationJump to search
1,357 bytes added ,  19:37, 1 December 2020
no edit summary
Line 161: Line 161:  
signal-event domain-create cloud.mydomain.com
 
signal-event domain-create cloud.mydomain.com
   −
#this one to let nextcloud dav be redirect correctly
+
#this one to let nextcloud DAV be redirect correctly
 
config setprop nextcloud CloudDomain cloud.mydomain.com
 
config setprop nextcloud CloudDomain cloud.mydomain.com
expand-template /etc/httpd/conf/httpd.conf
+
signal-event nextcloud-update
service httpd-e-smith restart
      
#only if you use a Let's Encrypt certificate
 
#only if you use a Let's Encrypt certificate
Line 170: Line 169:  
dehydrated -c
 
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
   −
#to let nextcloud accept this domain
+
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
OCC "config:system:set trusted_domains 10 --value=cloud.mydomain.com "
  −
</syntaxhighlight>
      
=== Mount with davfs on Fedora Clients ===
 
=== Mount with davfs on Fedora Clients ===
Line 281: Line 296:     
This appeared to fix the issue and the user could now see the files.
 
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 ===

Navigation menu