3,249
edits
Changes
From SME Server
Jump to navigationJump to search→Configuration
|string
|string
|main admin user for your installation (*)
|main admin user for your installation (*)
|-
|cliurl
|enabled
|enabled,disabled
|force overwrite.cli.url to https://domain/nextcloud or https://domain if virtualhost is set; disable it if you have specific needs and then use occ command to set your value
|-
|-
|DbName
|DbName
=== Uninstall ===
=== Uninstall ===
{{Warning box| if you plan to reinstall and had the nextcloud rpm installed do not yum remove it or rpm -e it as it would put you in a situation where you will not be able to reinstall and restore your old data. nextcloud-src rpm if present do not create such situation and can be removed safely.}}
{{Warning box| if you plan to reinstall and had the nextcloud rpm installed do not yum remove it or rpm -e it as it would put you in a situation where you will not be able to reinstall and restore your old data. nextcloud-src rpm if present do not create such situation and can be removed safely.}}
Uninstalling the rpms
yum remove {{#var:smecontribname}} {{#var:contribname}}-src
yum remove {{#var:smecontribname}} {{#var:contribname}}-src
rpm -e --justdb nextcloud
rpm -e --justdb nextcloud
those folders will then remain
those folders will then remain
and finally, db configuration with entry for nextcloud.
and finally, db configuration with entry for nextcloud.
If all of those remains as is, a simple reinstall of the contrib will bring back nextcloud running. If you uninstalled it because your install was non functional or want a complete removal, there are extra steps.
In case of deleting either the db or part of the software folder upon reinstalling the contrib it will just stall in the process to avoid to have db and software version not in sync.
In case of deleting either the db or part of the software folder, whenever you will try to reinstall the contrib, process will fail as db and files are not in sync.
In case you need to reinstall from scratch, '''first, backup what you might want to restore latter''':
cd /home/e-smith/files/nextcloud/data
mysqldump nextcloud > nextcloud55.sql
mysqldump105 nextcloud > nextcloud105.sql
config print nextcloud /root/nextcloud.config
tar -czf /root/nextcloud.tar.gz /home/e-smith/files/nextcloud/data /usr/share/nextcloud
then erase all what is remaining:
mysql -e "DROP DATABASE `config getprop nextcloud DbName`;DROP USER IF EXISTS `config getprop nextcloud DbUser`;"
mysql105 -e "DROP DATABASE `config getprop nextcloud DbName`;DROP USER IF EXISTS `config getprop nextcloud DbUser`;"
rm -rf /usr/share/nextcloud
rm -rf /home/e-smith/files/nextcloud
#this one is optional, and should not cause issue if still there
config delete nextcloud
and you should be able to start a new install from scratch
=== Release schedule ===
=== Release schedule ===
for installs done before smeserver-nextcloud 1.2.0-16, the rppm nextcloud was required and was conflicting with web update. Since 1.2.0-16 it is not required anymroe and we use a nextcloud-src rpm which updates itself in /usr/share/nextcloud-src and is only used if you install the first time or restart from scratch your install.
for installs done before smeserver-nextcloud 1.2.0-16, the rppm nextcloud was required and was conflicting with web update. Since 1.2.0-16 it is not required anymroe and we use a nextcloud-src rpm which updates itself in /usr/share/nextcloud-src and is only used if you install the first time or restart from scratch your install.
TO remove the nextcloud rpm which is not needed and save your files, two ways
TO remove the nextcloud rpm which is not needed and save your files, two ways
rpm -e --justdb nextcloud
rpm -e --justdb nextcloud
