I have an IHostedService app in dotnet core 3.1, which is deployed on azure app service plan, but it needs to browse the app service to activate IHostedService.
I have automatic deploy pipeline , when it deploy the IHostedService app,it stopped working and I have to start manually by clicking browse button.
Anyone know how to activate IHostedService after deployment?
One of my colleague who is devops expert find the solution for me.
App service -> configuration -> general settings -> Always On [on]
The Always On feature keeps your Azure web applications up and running,
Related
I am new to Azure Cloud and started working on App services. I created an app service through ARM templates from Azure Devops. Once done, I get the default page which is expected
Now, I deploy a sample react application to the App service and I see the application. However, when I re-run the ARM template, it takes me back to the default page. I am unable to understand why a re-run of ARM takes me back to the default page instead of my react app.
What can I do to have my react app up even after ARM template re-run? Is there any point I am missing?
I deleted my previous app service and re-did everything. Now, my application stays as is even after re-deploying the ARM template. Not sure what went wrong, the first time
If we are deploying a basic WebApp / WebApi, both these tasks from Microsoft appear to do the same thing - deploy to an appservice.
AzureWebAppV1
AzureRmWebAppDeploymentV4
How do you choose which one to use in a new YAML release pipeline? I just want to make sure I am using the version that is most future-proof - I have 25 release pipelines and don't want to have to re-do them unless necessary.
The way the help is written, hard to compare feature to feature to spot the key "must-haves". Some Microsoft online examples use both. Both are still marked as "In Development" in the readme and both are >1 year old since last check in.
The simplest way to deploy to an Azure Web App is to use the Azure Web App Deploy (AzureWebApp) task.
By default, your deployment happens to the root application in the Azure Web App. You can deploy to a specific virtual application by using the VirtualApplication property of the AzureRmWebAppDeployment task.
Azure App Service Deploy task allows users to modify configuration settings in configuration files (*.config files) inside web packages and XML parameters files (parameters.xml), based on the stage name specified.
Just my two cents, but I just noticed Web App Deploy takes much less time than Service App Deploy. I was wondering how come a simple zip deploy (Service App Deploy) can take so long. So I looked around and found there's also that Web App Deploy, so I tested it.
My project (React/Next small sized app) normally takes 6-10 min to deploy with Azure Service App Deploy (v4). With Azure Web App Deploy (v1) it took a little more than a minute. Wow.
I am using VSTS pipeline to deploy asp.net core 2.2 MVC to azure web app.
The last step which is deploy to azure fails - please see the error below:
##[error]Failed to deploy web package to App Service.
2019-01-08T21:39:47.3810424Z ##[error]Error Code:
ERROR_DESTINATION_NOT_REACHABLE More Information: Could not connect to
the remote computer ("our website url"). On the remote computer, make
sure that Web Deploy is installed and that the required process ("Web
Management Service") is started. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Error: Unable to connect to the remote server Error: A connection
attempt failed because the connected party did not properly respond
after a period of time, or established connection failed because
connected host has failed to respond ????:443
I even tried to Take App Offline but no luck:
However, it works fine if I publish the web app through Visual studio.
The problem was the subscription we were using has a firewall in place. So there was no way to get into firewall by even doing things like adding "WEBSITE_WEBDEPLOY_USE_SCM" = false in the app setting of web service.
The only solution we could think of was to create an agent inside a VM sitting inside the same firewall.
Recreate web app in Azure Portal -> Make sure target framework selected correctly.
I had accidentally set this to docker previously during my web app setup in the portal and this error was produced as well. I was using a MVC .NET 4.7 project and trying to use web deploy.
Hopefully this helps someone who has perhaps set up their web app incorrectly in the azure portal.
I upgraded my app service to Standard a few days ago. However, when I go to the backup configuration page, it never finishes loading. I just get the dots across the top of the screen forever.
According to your description, I have checked this issue. Per my test, I found I could not configure my backups for my mobile app on Azure Portal as follows:
While for web app, I could configure the backups via Azure Portal as follows:
Then I Use REST to back up and restore App Service apps and Use PowerShell to back up and restore App Service apps to check this issue. After configure the backup for my mobile app, I could see the Configure button on Azure Portal, but when I try to change the backup configuration, I encountered the same issue as you mentioned.
Per my understanding, you could leverage the powershell command Edit-AzureRmWebAppBackupConfiguration for a simple way to edit your Backup Configuration, you could refer to here for more details.
I'm starting out with IBM Bluemix and CloudFoundry. Using the tutorial examples of the Node.js/Cloudant app I have a dev workflow that seems really slow. What is the best practice for development with cf?
Here's what I do now
Edit my files locally
cf push myapp
Wait for a long time for the app to deploy
Test and find an error
Repeat
If you are building a Node.js application, you can use Bluemix Live Sync to quickly update the application instance on Bluemix and develop as you would on the desktop without redeploying.
You can choose to download the bl cli to sync with a local directory using Desktop Sync, or set up your project on DevOps Services and edit the code directly in your browser using Live Edit. Look in the documentation for Bluemix Live Sync.
https://developer.ibm.com/devops-services/2015/02/13/everything-kitchen-sync-bluemix-live-sync/
If you are doing more intensive development, it would be faster for you to set up node locally and push to Bluemix periodically. You can still consume most Bluemix services locally.
If you have to rely on an architecture resident in Bluemix and you do not have the possibility to test on local you cannot avoid the "push" command and the workflow you described. Regarding point 3, you might have incurred in a platform issue announced at https://developer.ibm.com/bluemix/support/#status.