mojo VS Flask

Initial thoughts

If you end up doing web development, check out Mojolicious:

https://mojolicious.org/

If you choose to go down the Mojolicious road, there's lots of deployment information and guides in the Mojolicious Cookbook.

I guess this will make it harder to search for Mojo(licious)-related stuff. 😩

But if I want the return value of 'test_p' or the error message 'This is an error', I can't seem to figure that out. I tried looking at the promise tests (https://github.com/mojolicious/mojo/blob/main/t/mojo/promise.t) but that didn't seem to work either.

Several! The 3 big players in order of release are Catalyst, (released in 2005), Dancer2 (Dancer was first released in 2009, but went through a complete re-write as Dancer2 around 2013), and Mojolicious (released in 2010).

This project sounds to me like the perfect excuse to learn Mojolicious if you're interested in converting your scripts into a web application using Perl.

Awesome! I still use Perl on a pretty regular basis both for work and fun. I really enjoy it. Definitely take a look at Mojolicious if you haven't already. It's primarily focused on being a web framework (both server and client), but it's nicely modular so you can use bits and pieces of the stack. In i3mojo, I used the Mojo::IOLoop event loop, Mojo::Base as a base class system, and Mojo::UserAgent as a web client for some plugins.

Last time I used Perl for anything web it was via https://mojolicious.org/

It even does event-based and websockets

I'd suggest Flask or some of the smaller projects in the Pallets ecosystem:

https://github.com/pallets/flask

#!/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.