-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment to Azure AppService - Guide #650
Comments
While you're at it... maybe immediately create a page on the docs site for it ;-) |
@DevJr14 as it's working fine now, maybe creating a small doc will be helpful for others too... :) |
Hi, yes it is working well both api and client app. I have already decided to create a documentation on Wednesday 11 May 2022. |
@fretje I have compiled a word document with screenshots. Could you help with how i should create a page? |
You mean for the docs site? @iammukeshm, can you set up a stub page for this, so he has to only fill it out? |
Yes that's what i meant. |
Done. @DevJr14 , you can pull the docs repository of fullstackhero. Here is the page I created for Azure Deployment Guide. You can use markdown formatting. https://fullstackhero.net/dotnet-webapi-boilerplate/tutorials/deploying-to-azure/ You can refer to https://github.com/fullstackhero/docs/tree/main/content/en/dotnet-webapi-boilerplate/fundamentals/logging for seeing how images are attached. Docs Guide - https://fullstackhero.net/basics/contributing/#docs |
Thanks @iammukeshm i shall do this over the weekend. |
Hi @iammukeshm I have just created a pull request in fullstackhero.doc project for this issue. I shall close this issue once the pull request is approved. |
Documentation added. |
Discussed in #649
Originally posted by DevJr14 May 7, 2022
Hi All,
Anyone who has successfully deployed to Azure AppService and willing to share detailed guideline on how to deploy?
A documentation which includes step by step processes with screenshot would be highly appreciated.
Thanks in advance.
The text was updated successfully, but these errors were encountered: