flask-base VS cookiecutter-flask

I'm trying to extend the flask-base project https://github.com/hack4impact/flask-base/tree/master/app. This uses the the application factory pattern in app/init.py and blueprints.

I came across (flask-base)[https://github.com/hack4impact/flask-base], which is a nice and robust boilerplate for large flask apps, you could use this as a reference point.

This can help you

May you want to see this

No GUI but you can use https://github.com/cookiecutter-flask/cookiecutter-flask to generate a skeleton project. I personally don't use it as it's too opinionated for my liking, however, may find you can get up and running quickly.

you can use any cookiecutter for flask. https://github.com/cookiecutter-flask/cookiecutter-flask have a look

A quick Google search can reveal so much. As a programmer you should be very capable of finding it yourself (;

Well look, I would encourage you to, and it's easy to, start from a position of knowing that your code will run on a server. You could use cookiecutter-flask, or you could just find a heroku template for a Flask app - cloning it and deploying it becomes quite simple, and it is helpful (IMO) to know for a fact that everything you're doing is going to work fine on the server, and to grow accustomed to working in a "I'm going to push this feature to the server when it's finished" type of workflow.

I take it that you have never heard of cookiecutter or the recipe for starting a flask project?

Cookiecutter flask is a template for large projects, it’s always a great place to start and compare against https://github.com/cookiecutter-flask/cookiecutter-flask