build-a-saas-app-with-flask VS gunicorn

I've been maintaining my Build a SAAS App with Flask video course[0] for 8 years. It has gone from pre-1.0 to 2.3 and has been recorded twice with tons of incremental updates added over the years to keep things current.

In my opinion tutorial creators should pin their versions so that anyone taking the course or going through the tutorial will have a working version that matches the video or written material.

I'm all for keeping things up to date and do update things every few months but rolling updates don't tend to work well for tutorials because sometimes a minor version requires a code change or covering new concepts. As a tutorial consumer it's frustrating when the content doesn't match the source code unless it's nothing but a version bump.

I've held off upgrading Flask to 3.0 and Python 3.12 due to these open issues with 3rd party dependencies https://github.com/nickjj/docker-flask-example/issues/17.

[0]: https://buildasaasappwithflask.com/

Build a SAAS App with Flask. Course / Boilerplate. https://buildasaasappwithflask.com/

Personally I maintain https://github.com/nickjj/docker-flask-example. There's also https://github.com/nickjj/build-a-saas-app-with-flask if you want more opinions.

Thanks a lot!

By the way the version of the course on Udemy doesn't get updated. The full version of the course is at https://buildasaasappwithflask.com/ which includes lifetime free updates (it has over 10+ hours of extra updates and new features not on the Udemy version). Udemy is a really bad platform for instructors which is why I've been trying hard to decouple myself from them over time.

As for a tutorial on using this repo specifically, did you find the readme file lacking in any way? I tried to write the readme to be fully self contained. It would expect prior Docker knowledge tho. I did give a talk at DockerCon going over a bunch of Docker best practices at https://nickjanetakis.com/blog/best-practices-around-product.... It was using a Flask example repo not Django but everything still applies. The same patterns are used.

Indeed, you can also create a Jinja macro to auto-insert the token into all of your forms too, here's a code example[0]. It's a 100% solved problem both on the Flask back-end and template side with an ability to opt out of it when you need to on the back-end such as accepting webhooks from another service.

[0]: https://github.com/nickjj/build-a-saas-app-with-flask/blob/1...

Gunicorn is one of my favorite app servers. I've been using Gunicorn in production on a bunch of projects (any Flask / Django project) for around 8 years now. It's rock solid and extremely predictable.

I also use Gunicorn in development too, it supports code reloading and also lets you enable Flask's debug middleware so you can use the interactive debugger. This is all configured in my Build a SAAS App with Flask course, a code example is here: https://github.com/nickjj/build-a-saas-app-with-flask.

That makes sense. Also do you have any experience with https://buildasaasappwithflask.com/ ?

Can’t speak to Corey Schafer’s, but I found this course here to be much better than Miguel’s https://buildasaasappwithflask.com/

I'm hoping so – gunicorn has a long-open pull request that would fix `--reuse-port`, which currently does nothing

https://github.com/benoitc/gunicorn/pull/2938

For building your API, I recommend using the Flask library. It is very beginner-friendly, and you will be able to build a simple API in a matter of minutes! Keep in mind that, for a more serious project, you should definitely use something like gunicorn to run you API as a production server.

Interesting looks like it might actually be a python bug. Somehow just changing from sys.exit(0) -> os._exit(0) apparently fixes it.

https://github.com/benoitc/gunicorn/pull/2820

Yep for production that works. In development tho I don't think the gunicorn --reload flag works with that worker type so you end up having to use uvicorn if you want to be able to code loading.

This may have changed but I remember this being an issue around 8-9 months ago the last time I checked and going back https://github.com/benoitc/gunicorn/issues/2339 it looks like the issue is still open.

The cool thing is that you can easily migrate your WSGI- application such as Flask, Django, or Gunicorn to AWS.

gunicorn: Python WSGI HTTP Server.

I did some googling and just realized I'm using ALB not ELB, not sure yet if that makes a huge difference for this particular issue. I found the github issue which unfortunately was closed: https://github.com/benoitc/gunicorn/issues/1194