Yes, turn that shit off… and rebuild in a very manual way (my backup/restore also crapped out) this entire site…. I have lost my cool Tag Cloud. Apparently, like a written blog… tag clouds out out of fashion… everyone wants to do video or podcasts with video… bah bah bah…

~Well I’m sure I will home some tech thing to go on about… shortly…

~SG

It’s very straight forward on how to do this for your App Service. And indeed for a domain that one owns this is simple to setup. Azure creates a CNAME and TXT dns records for one to push forward a domain or sub-domain to the Azure App Service (you know that horrible url that ends with “azurewebsites.net”). And this all works…. mostly.

It would appear initially that Permalinks can not be updated to point to the subdomain…

Yes that thing in the WP general settings… So how does on fix that? Well I dropped into the ssh dev tool on the site… This is located on the App Service here:

Push “go” – you may need to respond to a credential request… ***Warning THE SSH WILL PUT YOU IN THE CONTAINER AS ROOT!! yeah… be careful here.

Next, we is word press…. it’s here /var/www/wordpress. And if you think we are going to modify wp-config.php then yes we are. I suggest you cp a copy to a .bak file.

I cd’ed into the path /var/www/wordpress:

nano the file… nano wp-config.php ( you did do a cp wp-config.php wp-config.php.bak right?)

Next a couple of steps:

Step 1 comment out the ‘WP_HOME’ line (this is really all one needs to do… leave the WP_SITEURL the same)
Step 2 add a new line setting the ‘WP_HOME’  to the custom domain. ***you must have already set up a custom domain in Azure before you update the config file. If you don’t, yes your site will break!***

Save the file and re-enter your Dash Board in Word Press… You may have to restart the app and wait for the update to occur. But this should fix the peralinks.

~SG

I will be doing some testing here before I move and go the main site. This is the first step into the cloud with a site container with a WordPress site deployed. As it turns out doing this in Azure is very simple…. Now cloning my site from one host to another that was interesting. So Far the only issue was between Azure site caching with a WP Cache plugin- the plugin did not win that battle. Deactivating the cache plugin was the fix.

So that is the first step… more to come.

~SG

Looks like I will need to re-build the “massive”- as proxmox seems to have “eaten” itself… Yeap, not a hardware— it’s something else! Oh how I do live linux…

~SG

ScottGeek

And yet here we are. The gateway did not in fact give the same IP address to the main hosting server. Oh why Oh why?

Anyway, sites are backup again!

~SG

~ScottGeek.

• ASP.Core  3x – the latest going on’s since my last posting… which was ASP Core 2.1.
• Blazor – I’m dipping my hands into this now that it seems to be getting some traction
  (looks like EF core finally works in Blazor).
• The Age of “foldable” things is here?
• The Azure Cloud and what I’ve been up to in this space.

Those are my current tech workings… so we shall see.

~ScottGeek.

 It’s been a busy month and ½… It’s not that there’s not a lot to talk about… Indeed there is. Anyway, I’ve lots of Azure stuff to point out and comment on as I’ve completed a cert class on Azure dev (or so it was called). Then there’s ASP Core 3.x… some new versions of Visual Studio. And I’ve not even written anything on Media stuff… Star Wars… Disney+… the list goes on….

Well, I’ll be out of the corp life for a couple weeks coming… there will be time to do some catching up.

~ScottGeek.

So, you will notice the annoying Capcha- not perfect… but there are also spam controllers collecting you as well.  

My point is- Stop “bot-ing” my site (ya I know that’s never going to stop)… if you are real person and your comment does not show up… well it happens. I’ve too many hits on my firewall from Ad trolls, not everything is going to make it through.

~SG