The FastOpp project’s direction is clear: a modern serverless architecture that scales cleanly.
I'm not sure if this is the direction of the project. I believe this is one option, especially for people who want to deploy for free or have the ability to scale their project.
FastOpp is designed to be deployed with SQLite and local file storage for simplicity and ease of deploy. If you took 30 minutes to deploy the FastOpp demo, it's a long time. Realistically, I hope that the deploy would be shorter.
There are two components that take longer with Leapcell:
While both of these are great and have advantages, they are more difficult.
With the philosophy of FastOpp being simplicity, I don't think that serverless is the direction. I would call it a strong option.
Do not prefix with RUN in Leapcell’s UI.
Did you try using RUN and it failed?
So nor prefix with startup() in Leapcell’s UI.
Does it fail if you leave the default startup()?
FastOpp’s demo imports sample photos. Ephemeral /tmp storage is not reliable for user files.
I believe FastOpp downloads from unsplash, saves to a temporary area, then copies to a web directory. This is to avoid copyright and license issues. This is why there are photos and sample_photos in the storage.
/health /healthz /kaithhealthcheck
It does not use /health or /healthz. These are for different systems. Leapcell uses
/kaithhealthcheck and /kaithheathcheck. (no l)
Troubleshooting section is excellent. Add to the great parts of this post to the document that ships with FastOpp.
github.com/Oppkey/fastopp/issues/156
It would be great to extend the Troubleshooting section that involving students