That's really two operations: splitting the combined db to separate WP and Civi ones, and migrating. For the migration part see the manual.
To split the db, you could make a duplicate of the original as the Civi db (dump and load), then in the Civi one delete all the non-civi tables and in the original/WP one, delete all the civi tables. In your civicrm....
Is there somewhere in the docs where it says to go to https://github.com/civicrm/civicrm-core/releases because that isn't the right place to download and all you get from there is core, not the wordpress parts, so if it says that it should get changed.
You need to download from https://civicrm.org/download and if you need an older release you can go to ...
This is basically a system admin question rather CiviCRM specific. I personally don't have very good experience in doing this but when there is URL changes
Make sure your new domain is pointing to correct server IP
Update the url in apache or nginx conf.
Update .htaccess file in your site directory if its using any base url.
Update the base url in wp-...
If you are trying to get a different version of the wordpress download you can just swap in the relevant version number in the url
for example -> https://download.civicrm.org/civicrm-5.17.0-wordpress.zip
Welcome to SE! Setting up cron can be confusing since there are many variations and it touches several aspects: OS users & permissions, CMS users & permissions, other tools, cron - and the details depend on your hosting environment.
I've just re-read the page you linked to. It has the information you need, but it also has other options that you ...
found the answer
long ago, someone had added alias drush='/usr/bin/php5 /usr/local/bin/drush' to /etc/bash.bashrc I commented that out and all works as expected
I hit this same issue recently.
debian OS, php 7.1 on command line and in apache; same modules enabled; same configuration; can't see any differences between phpinfo() via apache and php -...
This isn't really a question specific to civicrm, but in general unless you never plan to upgrade or do any customization after the initial installation, you'll want to have the dev to production direction set up anyway.
I realize your situation isn't identical the one discussed here but I would try running the upgrade script to see if it resolves your issue.
If not - one important change is to make sure you remove the CiviCRM database tables when reinstalling! If you installed to a separate database from WordPress, that should be easy. If not, and it's not practical to ...