-
Notifications
You must be signed in to change notification settings - Fork 390
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
What are previous users of this repo using to deploy Django? #191
Comments
Thanks for taking care of the upgrade to Ubuntu 22.04. On my side, I'm still using this repo. Even if it is much less than in the past. |
Sorry for the delay (and thanks for all your maintenance work!) I still use a private fork of this repository (I've generally tried to upstream any changes I made). I'm on Ubuntu 22.04 in that fork. My goal is to move off Ansible, though, and towards a containerized deployment. So I do plan to eventually stop using the patterns in this repository. |
Thanks for your contributions and question. I use github actions and docker exclusively now. Something similar to what's described here: https://testdriven.io/blog/deploying-django-to-digitalocean-with-docker-and-github-actions/ |
@banagale thanks for your response! I'd love to hear more about how you're doing that, i.e., how are you provisioning the docker container? Is there a dockerfile/docker setup for Django and NGINX you've forked or did you just roll your own? |
No problem. There's another blog entry from that same group that focuses on the orchestration including nginx: https://testdriven.io/blog/dockerizing-django-with-postgres-gunicorn-and-nginx/ My setup is a mix of this and the deployment method in the prior link. |
I'm looking into upgrading this repo for Ubuntu 22.04 but wanted to ask those who have contributed before, are you still using this repo? If not, what are you using now to deploy Django?
@dpward @StuartMacKay @jcalazan @DavidCain @jpmjpmjpm @isedwards @banagale
The text was updated successfully, but these errors were encountered: