Deploying the backend to Azure #210
-
I have completed my first search-based messaging extension. Now all works fine in a local scenario by leveraging ngrok. I am at the point that I need to deploy to the client's environment and would like to know what is the next step. My first approach would be an AppService in Azure. What are my options ? Also, what are the best practices regarding environment specific configurations contained in the .env file ? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
Good question. There's multiple ways of doing this - and if Azure is your target cloud then running it in an Azure App service/web application is most likely your best option - and it's fairly easy to set up. I previously wrote a post on how I do this, for my projects, with Azure DevOps: https://www.wictorwilen.se/blog/deploying-yo-teams-and-node-apps/. The pipeline could easily be replicated for other CI/CD services. |
Beta Was this translation helpful? Give feedback.
-
Another option that you can use to deploy the solution is to user Containers and Docker. The scaffolded project already contains a |
Beta Was this translation helpful? Give feedback.
-
Thank you very much, this is exactly what I needed 👍🏻 |
Beta Was this translation helpful? Give feedback.
-
I have packaged my application as per the provided blog post. I have deployed to an Azure App Service and recreated the environment variables. However, the application keeps getting an HTTP error 500 from the bot framework when trying to POST to /api/messages. Local Setup works, I have tested the GraphConnection made by the bot, updated the bot messaging endpoint to target my App Service host name . The following is the error I keep getting: BotFrameworkAdapter.processActivity(): 500 ERROR Any idea what might be happening ? |
Beta Was this translation helpful? Give feedback.
Good question. There's multiple ways of doing this - and if Azure is your target cloud then running it in an Azure App service/web application is most likely your best option - and it's fairly easy to set up. I previously wrote a post on how I do this, for my projects, with Azure DevOps: https://www.wictorwilen.se/blog/deploying-yo-teams-and-node-apps/. The pipeline could easily be replicated for other CI/CD services.
When it comes to the environment variables, having a
.env
file is great for dev but I don't recommend it in production. Use either the Azure App Service configuration or even better Azure App Configuration (for the latter I created a small utility package that allows you to …