3,254
edits
Changes
From SME Server
Jump to navigationJump to search→Use a dedicated domain to connect to Nextcloud
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
signal-event nextcloud-update
#only if you use a Let's Encrypt certificate
#only if you use a Let's Encrypt certificate
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
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 "
=== Mount with davfs on Fedora Clients ===
=== Mount with davfs on Fedora Clients ===
