Zappa VS PyInstaller

If people aren't familiar, there's a similar project for Python that's fantastic: https://github.com/zappa/Zappa

Chalice was a consequence, a reaction from AWS to the release of (Zappa Framework)[https://github.com/zappa/Zappa] that provide a very good alternative to migrate very quickly a Django/Flask or any WSGI compliant solution in Python.

Use Zappa https://github.com/zappa/Zappa and host as a Lambda, simple setup and deployment, Lambda only costs when processing requests, no servers to mess around with

One of my favorite options that is probably the most cost-effective is to deploy using a 'severless' model on AWS Lambda using zappa which supports deploying Python webapps to AWS in this way. Zappa also makes it super easy to deploy in just a couple commands! The README includes instructions for everything you might need, including handling sensitive information like your database passwords, running django management commands, setting up DNS, etc.

Deployment works nicely with Docker. I often use AWS AppRunner because it's really easy and just scales. Some people use AWS Lambda with Zappa but I don't recommend it unless you really want to spend less than $15 a month. You will probably need Django Storages to save uploads to an S3 bucket. At some stage you might want to put a CloudFront distribution in front of everything but the configuration of the caching behaviour might be a bit confusing when you do it the first time.

It doesn't have to be an either-or! I have several apps in production that were developed on Django or Flask, and deployed to Lambda using Zappa.

If you need a relational DB, you can use AWS Aurora or RDS and use cloud functions ('lambda' in AWS) that you can invoke with HTTP to process the document first. Zappa will do a lot of the configuration for you if you go that route.

Lambda + API gateway, this library bundles a Django application into a lambda https://github.com/zappa/Zappa . 1 million free invokes from aws, scale to zero, plugs into your RDS

I use Zappa, it just schedules a frequent execution of the lambda: https://github.com/zappa/Zappa#keeping-the-server-warm

Not sure if fixed in this patch, but pyinstaller had an issue in 3.12.0 https://github.com/pyinstaller/pyinstaller/issues/7992

You are right. I think I've misremembered the module name - it was uwsgi, not uvicorn.

This is a github issue where I discussed my original issue with PyInstaller devs - the dev explained the situation very well: https://github.com/pyinstaller/pyinstaller/issues/6362

PyInstaller seemed like the most maintained and developed tool to freeze python script into an executable, so I went with it. As expected, the freezed interface with the model was gigabytes large, so I had to figure out how to squeeze this. Fortunately, Onnx worked wonders and packaged the model into an inference only state, so I could throw away the Pytorch and Torchtext dependencies when freezing with Pyinstaller.Now the size of the executable with the model was 43MB instead of 4GB.

You might want to see Pyinstaller and auto_py_to_exe if you want a GUI interface.

It uses the pyinstaller command behind and please read their docs if you want to know more details.

I also found another link on github that may have some solutions to try: https://github.com/pyinstaller/pyinstaller/issues/3600

I made a Django react app. Now I want to make it a desktop application so that the user does not have type python manage.py runserver and also activate the environment every time. I used pyinstaller. I did all the steps mentioned for django

First, instead of creating a VM for windows, you may need to use a software called Wine mentioned in the pyinstaller FAQs