Hi, I have a test site at: mydomain.biz The site is replacing a current one on another server/not with laravel forge ie: mydomain.com
So my test site is now ready to replace the .com site. In a perfect world I'd like to simply go into Laravel Forge and change the .biz domain name to .com and then repoint the DNS etc to the laravel forge IP the site is on.
Anyone see how this could go wrong for me? I don't really know if changing the domain name in forge will do the trick or not or is there some repercussions I'm not aware of.
Its just the DB and all the data and all the additional work/tweaks I've done would be easier to make the domain change and start using it as opposed to creating a new site and then having to get all the DB data etc. etc. over to it
Why don't you just rollout the mydomain.com site in forge? You can connect your site to the existing database on your forge server in your .env file. You can change the domain name, but I guess that you'll have to edit the ngnix host settings as well. I believe that forge is not managing that.
Please or to participate in this conversation.