You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 9, 2022. It is now read-only.
I followed your guide to the tee (it's really detailed and well written, thanks!), and I've gone through it a twice and I just see the default Azure page that says "Your app service is up and running. Time to take the next step and deploy your code." and not the Django page.
I'm scratching my head because I have 4 tutorials open, all of them are fairly straightforward and identical, and all of them are saying it should just magically appear. Any chance you can shed some light on what's changed?
The text was updated successfully, but these errors were encountered:
The last one helped, my app required a custom startup command. I think it might be worth adding to your guide because I have done nothing different, but wsgi module isn't in the project root, but two folders in. Thank you for your excellent guide!
I followed your guide to the tee (it's really detailed and well written, thanks!), and I've gone through it a twice and I just see the default Azure page that says "Your app service is up and running. Time to take the next step and deploy your code." and not the Django page.
It seems that even after deploying from Github Actions, Azure isn't picking up on the fact that it is a Django app. Azure gives the suggestion of this page: https://docs.microsoft.com/en-us/azure/app-service/configure-language-python#container-startup-process?appservice=startup
I'm scratching my head because I have 4 tutorials open, all of them are fairly straightforward and identical, and all of them are saying it should just magically appear. Any chance you can shed some light on what's changed?
The text was updated successfully, but these errors were encountered: