Moving database role only and wp-config.php database server

xyzulu

I have no issues moving sites manually as well as understanding how the database host setting in wp-config.php works. But maybe I am missing something here.

Enhance moves database "roles" to another server just fine.. but makes no changes to the wp-config.php file. I understand this would add another check to the process.. ie if the site runs Wordpress update this value. Moving a Wordpress website along with the database to another server is seamless and so simple with Enhance.. but not just moving the database.

Did I miss something? (and I know this is Wordpress specific)

MediaServe

Use mysql.[domain name] rather than localhost in wp-config.php and it'll move fine wherever the database lands. DNS propagation might delay it a bit until enhance develops the proxy DNS stuff though.

xyzulu

Good suggestion, but Enhance installed Wordpress still use localhost .. so I still need to do some editing.

pratik_asabe

xyzulu Good observation..

Recently i encountered same observation when we were doing some trials for seperate db server to share load and increase performance, i had also discussed with Adam regarding and we concluded we can not use separate db server yet, not without manual interventions at least.

first, there's no dynamic updates happening in wp-config.php even if there's a dedicated DNS entry present for mysql, which is waste bcz it has no use as of now, enhance should utilize that DNS entry to use it in db host parameter in wp-config.php after detection of seperate db host IP.

secondly, separate db work fantastic in private network but unfortunately as of now enhance doesn't support private networking communications so we have to rely on public connection which will use bandwidth and add extra ms of latency!

MediaServe

xyzulu Good point! I was just checking a new client who installed WordPress from scratch, and although we have separated db and app layers for WordPress hosting, the db layer still exists on LiteSpeed so the db and app layer caused the new client to have them on the same server (planned to remove the db layer at some point to prevent that, but it takes time.) So it appears you're correct and localhost was used. I'll have to remove the db layer from the LiteSpeed server and then try installing WordPress and see what happens.

Other newer shared hosting clients have app (OLS) and db combined, and all cPanel migrations have everything combined so I haven't really seen how the WordPress install works. If a separate app and db layer for a website, will WordPress installation fail? I'll have to see when I move everything off I guess.

Really wish Enhance had begun MariaDB sooner, because we now have a mix of MySQL and MariaDB which is a royal pain moving things back and forth. <sigh>

xyzulu

MediaServe I'll have to remove the db layer from the LiteSpeed server and then try installing WordPress and see what happens

That’s a smart idea.

netzen

For me, for example, after migrating sites from server to server, the old IP address remained in wp-config..

/** Database hostname */
define( 'DB_HOST', 'xx.xx.xx.xxx' );

That's not very user-friendly

So I'll try changing it manually and see...

kess

Why don't you use the hostname instead ?
Why is everybody stuck in using IP Addresses ?

netzen

kess wp-config was originally filled in automatically by Enhance. And the original site had a remote database. Already resolved by manually renaming it to localhost. The new server has Applications and databases in one place.

slimx

I think everyone is missing the point.
OP is saying...

By default it is installing and saying 'localhost'. It is strange that we have the capability, and that enhance even creates the dns record for it but does not implement it into the WP install.

I think the expectation was for Enhance to auto-adjust the WP-CONFIG file to the hostname if you decide to move it to another control panel. And by default having it NOT set to localhost might make it slower; so that is out of the question.

But.. PERSONALLY...
Considering only the host should have control over where the database is, and having US do the manual labour work i think is fine. I actually would vote to get rid of that dns record, im sick of deleting it lol.

My Vote Solution:
Similar to how we have a DNS TEMPLATE. We should have a WP-CONFIG template.
I personally have to turn ON wp-cron all the time, because enhance installs it OFF by default. Very annoying.
A lot of themes and their demo import for some reason only works if WP-CRON is enabled.