On wordpress app-service

Question

On wordpress app-service

Gayathri Anbarasu 40

When deploying initial stage of my wordpress production application, it has deployed on developed php wordpress. app-service on windows and configured run-stack as ASP.NET version 4.8 platform on 32 bit.

I am planning to do version-up on wordpress this month.

+++++++++++
I understand that WordPress primarily runs on a "LAMP" stack, which stands for Linux operating system, Apache web server, MySQL database, and PHP programming language; essentially, WordPress utilizes a Linux server with Apache to serve web pages, while storing data in a MySQL database and using PHP to process information on the backend.

++++++++++++
Does the configuration settings will affect my wordpress version update at on any cause?

Can I try same settings versionup on qa? or should I need to change this settings before versionup.
As my AZURE app-service os configured on WINDOWS , Will it be fine to keep same?

If am trying same, could you please suggest me what things need to pay attention on current case.

Accepted answer

2 additional answers

Your answer

Answer 1

Hello!

Just so you know, with your WordPress application currently running on an App Service configured for Windows, this means you're still using PHP 7.4 or an earlier version. This is a deprecated configuration on App Service, and you should consider migrating to the WordPress container on App Service, which runs on Linux. This will ensure better compatibility with WordPress, improved performance, and continued support for PHP updates.

To answer your question about testing the version upgrade in a QA environment, the best approach is to use a deployment slot in Azure App Service. Here’s a simple way to do it:

Go to the 'Backups' blade on your Azure App Service in the Azure Portal.
Choose "Restore" and restore the backup to a new deployment slot on your App Service. This will copy all files from the time of the backup.
Restore a database backup from roughly the same time to a new database schema name to be used by the slot.
Update the configuration in the new slot to point to the restored database.
Check wp-config.php and update the siteurl and home constants if needed.
If your site is a multisite, use WP-CLI or a similar tool to update the database URLs to match the new slot URL.
Test your new slot, make any necessary configuration changes, and verify that everything is working properly.

Once everything is confirmed to be running smoothly, you can use this to confirm configuration changes and updates will function correctly.

Again, please consider migrating to the WordPress container, as this will provide the best support and compatibility in the future.

Gayathri Anbarasu 40 Reputation points

2025-03-03T04:23:43.75+00:00

Thank you so much for answering my question. Much helpful.
Actually When I clone the current prod environment to the staging slot, app and config will be clone right?
Do i need to manually deploy the application?
Additionally my environment uses custom domain, When I try to clone custom domain to default domain, It is not working correctly 403 Error raises.
I checked settings>custom domain> staging URL registered automatically without certificate. All config/settings mirrors according to PROD .
Still why the error shows. can anyone knows?
< I understand we can add this staging default URL as C record on domain name registered site.>

Answer 2

Manu Philip 20,206 MVP Volunteer Moderator

Hi Gayathri Anbarasu

If you are on a Standard or Premium plan of App services, you can add a deployment slot in your web app setup, which will help to test any changes before being deployed in production environment. So, as a first step, you need to upgrade the plan, if you are in basic plan

After upgrading the plan, you can add a deployment slot from here:

User's image

While, creating the slot, make sure that you are cloning the existing website

After the deployment slot has been created, you will have the exact copy of the website within the same LAMP version as the production has.

Now, you can try your version changes in the deployment slot and test it. For that, open the deployment slot created and change the versions as needed

Hope this helps in addressing your concerns.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Gayathri Anbarasu 40 Reputation points

2025-02-26T02:18:11.88+00:00

Hi Manu San,

Thank you so much for answered my question. Much helpful.

Can you clarify about the database on this case?

while cloning the existing website, database will be create on same instance right? same instance with different database.

I do version-up and I do test is fine on deployment slot.

When we are going to swap our deployment slot with prod, How the database will act on this.

I need to swap my database also. Because WordPress will get update on both core files as well as database update. So I am planning to swap both. what caution's do I need to take care . If you aware of this kindly share with me.

As of my understanding , during the swap operation app-core-files as well as configuration will get swap , But database wont swap. So the prod application will take staging database, and staging slot database will take prod db as reference from configuration file.

can we continue this state till end? Our prod is taking slot db hereafter. only the change is DB name. There is no worry because both DB schema is in same DB server azure.

so no need to worry right?

Please clarify my doubts.

Thank you
Manu Philip 20,206 Reputation points MVP Volunteer Moderator

2025-02-26T04:36:03.26+00:00

I hope, you have enough information on your question now!

Answer 3

Gayathri Anbarasu 40

Hi Manu San,

Thank you so much for answered my question. Much helpful.

Can you clarify about the database on this case?

while cloning the existing website, database will be create on same instance right? same instance with different database.

I do version-up and I do test is fine on deployment slot.

When we are going to swap our deployment slot with prod, How the database will act on this.

I need to swap my database also. Because WordPress will get update on both core files as well as database update. So I am planning to swap both. what caution's do I need to take care . If you aware of this kindly share with me.

As of my understanding , during the swap operation app-core-files as well as configuration will get swap , But database wont swap. So the prod application will take staging database, and staging slot database will take prod db as reference from configuration file.

can we continue this state till end? Our prod is taking slot db hereafter. only the change is DB name. There is no worry because both DB schema is in same DB server azure.

so no need to worry right?

Please clarify my doubts.

Thank you

Bhargavi Naragani 6,050 Reputation points Microsoft External Staff Moderator

2025-02-27T00:40:20.3166667+00:00

Hi @Gayathri Anbarasu,

When you clone your site into a deployment slot, the app files and settings are copied, but not the database. If you create a different database for your staging slot (such as a QA environment), your wp-config.php will reference this new database.

When you perform a slot swap (such as from staging to production), only the app files and settings switch over, not the database. So, if your staging slot has its own separate database and you switch slots, your production app will begin to use the staging database, and the previous production slot will reference the production database.
It's fine if both the databases are on the same Azure DB server and you're sure about the updates of the staging database. But here's what you need to be make sure about:

Ensure your staging database has the latest data and schema updates.

Always do a complete backup of the prod database prior to the swap.

Double-check your connection strings in the App Service configuration for both slots before and after the swap.

After swapping, ensure the production location is operating as expected and accessing the proper (and current) database.

If you prefer the safest method, rather than switching databases, leave your production application pointing to its own database and update WordPress against it directly after testing on staging.

Please refer to the below documentation:
https://learn.microsoft.com/en-us/azure/app-service/manage-backup?tabs=portal
https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots?tabs=portal

if you have any further concerns or queries, please feel free to reach out to us.
Bhargavi Naragani 6,050 Reputation points Microsoft External Staff Moderator

2025-02-28T00:54:25.0333333+00:00

Hi @Gayathri Anbarasu,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Bhargavi Naragani 6,050 Reputation points Microsoft External Staff Moderator

2025-03-03T03:14:29.2333333+00:00

Hi @Gayathri Anbarasu,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Gayathri Anbarasu 40 Reputation points

2025-03-03T10:15:22.9533333+00:00
Thank you so much. I also understand your reply on this . Much helpful.

Wordpress version update on Custom domain- I followed below steps:

I have created deployment staging slot

I do enable access restrictions - allow all

i have created staging database and imported prod tables into it.

I do app restore from prod to staging

wp-config i change database name to staging db - as it is not taking environment variables

On database- wp-options i changed site url and home url.

I do version update

swap- preview

swap

actually during swaps- connection strings also swaps - so prod will point slot db , . As my slot db is in same server, i am planning to use slot db and delete old prod database- as no longer use of old one- will it be fine to do delete this ?
Bhargavi Naragani 6,050 Reputation points Microsoft External Staff Moderator

2025-03-03T19:18:41.0833333+00:00

Hi @Gayathri Anbarasu,
Your method is generally correct! However, before deleting the previous production database, I would suggest taking a bit of care.

Double-check that your production site works well after the switch — check that all pages, plugins, and functionality are working as anticipated with the slot database.

Even if you're sure the old production database won't be required, backup it completely using Azure before deleting. That way, you've got a fall-back position if something goes wrong.

Leave the old production database up for a short time, perhaps a week in case you realize that there's some missing data or problems after the swap.

Once you're positive that the new database is running flawlessly and the older one is no longer in use, then you can proceed and delete it safely.

if you have any further concerns or queries, please feel free to reach out to us.
Gayathri Anbarasu 40 Reputation points

2025-03-04T05:03:57.84+00:00

Hi Bhargavi ,
Thank you so much.

I will follow the same.

When I am trying to clone the production environment to staging environment, I cannot get connect staging URL. As it is custom domain, I did restore to staging as well as I changed wp-config.php database details, connection string settings as well as staging db separately to link staging env. I changed home/site url on wp_options table too. .

After I made changes , When I hit staging URL, it will redirect into production url.

I cleared the browser cache, still same result.

can you help me on this.
Bhargavi Naragani 6,050 Reputation points Microsoft External Staff Moderator

2025-03-04T19:36:20.3966667+00:00
Hi @Gayathri Anbarasu,

Check wp-config.php, ensure below lines are configured properly for the staging environment. This overrules database settings for site URL and home URL, a very useful setting when transferring environments.

define('WP_HOME', 'https://your-staging-url.com'); define('WP_SITEURL', 'https://your-staging-url.com');

Double-Check wp_options Table, you might have already done this, but just check again one time, both of these should point at your staging URL.

SELECT option_name, option_value FROM wp_options WHERE option_name IN ('siteurl', 'home');

If you're using a caching plugin (such as WP Super Cache or W3 Total Cache), wipe out the WordPress cache via admin panel. In case you're not able to access the admin panel, remove the cache directory from wp-content/cache using FTP or Azure console.

Double-check there isn't a redirect rule that sends all to the production URL.

You can access staging WordPress admin, go to Settings > Permalinks and simply click on Save Changes (even if nothing changed). It resets the URL structure and fixes some redirect issues.

Share via

On wordpress app-service

2 additional answers

Your answer