Flask VS Masonite

#!/usr/bin/python # # https://flask.palletsprojects.com/en/3.0.x/installation/ # from flask import Flask, jsonify, request contacts = [ { "id": "1", "firstname": "Lorem", "lastname": "Ipsum", "email": "[email protected]", }, { "id": "2", "firstname": "Mauris", "lastname": "Quis", "email": "[email protected]", }, { "id": "3", "firstname": "Donec Purus", "lastname": "Purus", "email": "[email protected]", } ] app = Flask(__name__, static_url_path='', static_folder='public',) @app.route("/contact//save", methods=["PUT"]) def save_contact(id): data = request.json contacts[id - 1] = data return jsonify(contacts[id - 1]) @app.route("/contact/", methods=["GET"]) @app.route("/contact//edit", methods=["GET"]) def get_contact(id): return jsonify(contacts[id - 1]) @app.route('/') def root(): return app.send_static_file('index.html') if __name__ == '__main__': app.run(debug=True)

I was looking at all the big projects like numpy, pytorch, flask, etc.

Explore here.

I may use Flask-Admin initially to offload the "CRUD" operations to have an initial prototype fast but then drop it ASAP because I don't want to write a "flask-admin application" to fight against later on. If the application is mainly "CRUD", then Flask-Admin is suitable.

Now...

Would you do a breakdown/list of all the jobs you've done by sector/vertical and by function/role and by application functionality?

- [0]: https://flask.palletsprojects.com

- [1]: https://flask-admin.readthedocs.io/en/latest

- [2]: https://flask.palletsprojects.com/en/2.3.x/patterns/celery

- [3]: https://sentry.io

- [4]: https://posthog.com

- [5]: https://www.docker.com

In the lab to follow, we will be setting up an end-to-end DevOps workflow for a Flask microservice with GitHub Actions, using a self-managed custom runner for maximal control over the pipeline execution environment and automating deployments to a local Kubernetes cluster. Furthermore, we will construct separate pipelines for our "development" and "production" environments to further elaborate on the concepts of continuous deployment and delivery.

Flask Micro web Framework: You will use Flask to build a Flask web application.

In an earlier post I mentioned a bunch of Open Source web applications. Let's now focus on the ones written in Python using Flask the light-weight web framework.

I also suggest that once you've gained familiarity with the basics, you look at micro-frameworks, such as FastAPI and flask, before switching to a full fat framework like django, which will give you an appreciation of what opinionated frameworks such as django can do for you.

I would suggest Masonite [0]. It’s lightweight enough to replace Flask and has a plethora of built in features if you need to build a “production-ready” app. It tends to imitate Laravel in its project setup and naming conventions which, depending on your preference, can either be a boon or a bane.

[0] https://docs.masoniteproject.com/

Masonite is a wonderful Python framework, much similar to Laravel I found in 2018. I even chatted with Joseph about it in the old Slack channels, before the community moved to Discord.

Masonite Framework: https://github.com/MasoniteFramework/masonite

Exceptionite 2 is a debugging screen package written by the Masonite team. Although written by the Masonite maintainer team, it can be used in Flask, Django and of course Masonite.

If you want to learn more about Masonite, visit the GitHub page here: https://github.com/MasoniteFramework/masonite

For those who like the concept and want to encourage the developer please don’t hesitate to give a little star for Masonite on Github: https://github.com/MasoniteFramework/masonite