In this tutorial, I will be going over to how to deploy a Django app from start to finish using AWS and EC2. Recently, my partner Tu Vo and I launc...
For further actions, you may consider blocking this person and/or reporting abuse
Still in beta but now you can run your Docker compose files directly to Amazon ECS.
docs.docker.com/engine/context/ecs...
It abstracts a lot of the manual set up in the AWS console.
Awesome! Thanks for the heads up!
I will have to give it a try and update the guide.
Hi Ryuichi! Thanks for your post. I followed it, and I can browse to my django project. However, the admin site does not load any CSS. I collected the static files and double checked the nginx config to no avail. Any hints?
Don't worry! I found my mistake: the /home/user directory did not have execution rights for its user group and others. So, I changed the permissions by running:
Hi Jorge!
Sorry for the late response and for not being able to help you. I wrote this guide a couple of years ago so some things might be out of date. Your comment will help anyone who runs into the same issue again so I really appreciate your comment!
Hi Ryu, saw your profile on Twitter. I'm was just recently deployed a django app to a VPS. Though I followed a different method. Curious whether you have recommendation on project deployment once a project is up and running. (pulling newest version from github repo to server)
Good stuff btw!
I'm launching my own app to AWS with you setup, thanks a lot for sharing. I have one question though. Don't you need RDS when building for production ?
Hi Jose!
Thank you for checking out my guide!
Good point and I think I did not mention it but yes using either RDS or some other database service would be necessary.
For my personal project, I used ElephantSQL for a Postgres database as it was free but you are free to use whichever database works best for you!
I might do a follow-up guide on setting up a database with AWS when I have the time...
Thanks for replying, I'll be waiting for your follow-up. Keep it up!
I failed to start guvicorn, its saying failed to gunicorn.socke failed, also in status its inactive
is it necessary to turn on the 8000 port on inbound security group, once we set up Nginx/Apache for the static contents. The port for apache/nginx could get the requests right?
yes it is necessary to add 8000 port on inbound security group..
I'm just a beginner to this, can anyone explain why the docker is being used here?