Support

Just finished developing a joomla based site on a subdomain (https://dev.host.tld) of the host where the subdomain created a /dev subfolder on host root, where the site should go live (https://www.host.tld) . Now, since it's both on the same server what would you recommend i do. Usually i use my FTP client and move the files/folders 1 directory (after i clean up the root directory of course), make a new database and copy over the tables and change

public $log_path = '/home/<user>/domains/<domain.tld>/public_html/dev/administrator/logs';
public $tmp_path = '/home/<user>/domains/<domain.tld>/public_html/dev/tmp';

to

public $log_path = '/home/<user>/domains/<domain.tld>/public_html/administrator/logs';
public $tmp_path = '/home/<user>/domains/<domain.tld>/public_html/tmp';

in configuration.php

Which is a manual tedious manual process in which many things could go wrong.

Or would the site transfer wizard be a better option? Never used it before. Is it easier/possible to use it to "move" the site from the subdomain to host root and keep the database where it is (no need to create a new database/copy tables over etc)?

domain and subdomains are protected with an SSL certificate by let's encrypt. But i don't know if the host supports stfp and how to even use it.

For me, the easy way would be to do a backup, copy it to the new location, extract it with Kickstart and do the restore, using the same database. If you're done with the development site, there is no need to keep the separate database. I know how to use Kickstart, I wouldn't struggle with the Site Transfer Wizard for a one shot deal. The restore (or the Wizard) will take care of your paths, etc. in configuration.php and the paths in Akeeba Backup. You may need to edit the URLs at the bottom of the .htaccess Maker screen and re-generate your .htaccess file.

If you want to move the files, you can edit the database settings in configuration.php too and avoid the new database and copying the tables. It's a bit risky but it you mess it up, just copy the configuration.php file from the dev site again and start over. This way you may have to change your backup path in Akeeba Backup, depending on how it is set up. You may also have to change the .htaccess file as above.

I took your idea of full backup & kickstart. Easiest solution. Created new database, entered new credentials during kickstart and was back up and running. All i needed to do then was "fix" the backup directory in akeeba backup to the now siteroot and exclude the dev subdomain. Up and running in 5 minutes :) Not quite 7GB but still ;)

going to enable referral url's for a month so i can catch dead links and fix them :)

Problem solved!

I'm glad that worked for you!