I have just installed owncloud server and at the end of the instalation process, I didn’t realise I could change the db parameter. Now the owncloud server is runing with SQLite. Is there a way to go back in the instalation process. I have nothing on my owncloud server yet and I have configured the MySQL parameters.
Can I just change the config.php ‘dbtype’ => ‘sqlite3’, to ‘mysql’ ???
I have re-installed owncloud and now it says this, when I go to localhost/owncloud/...
"This ownCloud instance is currently in maintenance mode, which may take a while. This page will refresh itself when the ownCloud instance is available again. Contact your system administrator if this message persists or appeared unexpectedly. Thank you for your patience."
If yes, you would have to set up a mysql database, for that you would need to install a mysql server, then create a database for owncloud, and then run the occ command to convert from sql lite to mysql
php occ db:convert-type --all-apps mysql oc_mysql_user 127.0.0.1 new_db_name
You have installed owncloud, right? As final step you would to to the ip address and finish the installation. But if you want to use mysql, you can install the mariadb-server and php.7.0-mysql modules, then log in to the db-server, create a db, with user and password, then go to the ip for example localhost/owncloud, choose the mysql database instead of sql lite, enter the credentials, and then you will have a mysql database with owncloud
When you convert the database from SQLITE to MYSQL, do you need to be in any specific directory, or can you just run the command from anywhere? Also, will it only convert the specific database for OwnCloud and leave other databases associated with other applications alone alone? Final point, does it automatically update the config.php file to reflect the new database? Currently my config.php file is showing me that OwnCloud is using SQLITE3 as a database.
I take your point DeepDiver1975, but to be honest, when I started out I thought along the lines you mention, and what started out as a test installation has grown into something a bit more sophisticated.
Ok, so why do we include the procedure in the manual?
Surely it would be easier to simply state that it is not currently possible to perform this function, and so set up your installation using Lite or Full MSQL from the start.
Personally, I think the continued use of SQLite is a pain in the butt.