Azure / Azure/azure-quickstart-templates
Deployment works fine. The userscrip after that is failing.
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
[django-app] https://github.com/Azure/azure-quickstart-templates/tree/master/django-app
### Issue Details
Initial deployment works smooth - vm is setup, storage is set up, all fine!
Then the script (https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/django-app/install_django.sh) gets called. Things fail here. I assume between then and now - they way WSGI / apache might have changed - hence these errors now
Issue:
After a clean install, when I go to the fqdn - Error is
"The requested URL / was not found on this server'
I tried:
Logged in and restarted apache and app again. Got an error regarding server name. So checked ServerName $1. $1 was not populated. I hardcoded my server name. Tried again, now getting a 400 error.
### Repro steps (*if necessary, delete otherwise*)
1. Deploy to azure using https://github.com/Azure/azure-quickstart-templates/tree/master/django-app
2. Check deployment succeeds (it did in my case)
3. Visit the FQDN you set up. (xxxhelloworldnew.eastus.cloudapp.azure.com)
4. The page will be an error.
5. My debug showed something in the post-deployment script is not working as expected (https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/django-app/install_django.sh).
Kindly help!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the django-app template and its install_django.sh post-deployment script. Deploy the template to Azure, visit the configured FQDN, and inspect the Apache/WSGI setup and resulting errors, including the ServerName behavior described in the issue. Done means a clean deployment serves the Django app at the FQDN without the reported 404 or 400 errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, azure, django, shell
- Domain
- backend, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100