python-getting-started VS elastic-beanstalk-roadmap

For those of you who are new to Python (as I am), I used the Getting Started on Heroku with Python documentation as a helpful guide.

After setting up a Heroku account, we’re nearly ready to deploy. Let’s walk through the steps.

I did set that as the video tutorial from codemy.com that I was watching instructed to do so. But I was able to solve this issue I believe by following the settings.py file on this Github repo (which included moving the whitenoise middleware after the security middleware) and adding STATICFILES_DIRS = BASE_DIR / 'static' (along with deleting the old syntax that I had commented out) while following the steps (including manually running 'python manage.py collectstatic') on this Stack Overflow answer. Now time will tell if the static files will persist or if I will run into an issue when the Heroku dyno restarts.

Here's Heroku's own guide to hosting a python site: https://devcenter.heroku.com/articles/getting-started-with-python

2. AWS Elastic Beanstalk

AWS Elastic Beanstalk - An easy-to-use service for deploying and scaling web applications and services.

AWS Elastic Beanstalk (aws.amazon.com)

My previous workplace was run by a team that lacked experience in getting an app from zero to production. We had a starter react + rails app in our hands, but the details of the final step--putting our app online for users to consume--was amorphous at best. Our whiteboard was inked with a "let's use Elastic Beanstalk," so I was told to do just that.

Based on the fact that your ideal is to have a similar experience to heroku than managing your own server setting up reverse proxies take a look at these options:

1) https://dokku.com - lets you turn your light sail instance basically into heroku

2) https://render.com

3) https://fly.io

4) If you have aws credits this is their heroku equivalent: https://aws.amazon.com/elasticbeanstalk

above is not what I do but would be the options I would pursue if I understand your preference and requirement correctly.

Elastic Beanstalk (EB) is a cloud deployment service provided by Amazon Web Services. It facilitates the deployment and scaling of web applications and services by automating the creation of individual infrastructure components, including EC2 instances, auto-scaling, ELBs, security groups, and other infrastructure components. Using the AWS Management Console and command-line interface, deployment with EB is quick and simple. Although EB automatically handles your application’s deployment, the developer retains complete control of the AWS resources that run the application and may access them at any time. This is important, and it is a top benefit of using this service.

This Terraform code snippet can be used to deploy an AWS Elastic Beanstalk environment:

K8s isn't going to play well with your deployment pattern without some advanced cluster management. Honestly it seems like you would be better serviced with something like https://aws.amazon.com/elasticbeanstalk/ .