flask-static-digest VS flask-restful

I wrote an extension https://github.com/nickjj/flask-static-digest which digests your files by md5 tagging them so you can cache bust them and an optional config option I added was to be able to set FLASK_STATIC_DIGEST_HOST_URL = "https://cdn.example.com" but it never occurred to me you could just set static_url_path to https://cdn.example.com to get the same effect without needing to do anything extra in the extension. Going to investigate this approach and patch flask-static-digest if it turns out that it works.

This isn't built into url_for but it is built in with static_url_for which comes from the https://github.com/nickjj/flask-static-digest extension. Other frameworks like Rails, Django, Phoenix, Laravel and others have this behavior too.

In another reply someone else mentioned using Flask-Static-Digest which I highly recommend using in production. It will add a unique identifier (an md5 hash) to all of your static files so you can cache them forever with a proper web server but if they change, they will get a new file name to bust the cache.

Flask-Static-Digest for md5 tagging / pre-gzipping assets and optionally configuring a CDN

Among other things the https://github.com/nickjj/flask-static-digest extension used to throw 500s for missing assets in production mode because it would try to do a dictionary lookup on a key that didn't exist which threw a Python error.

When it comes to Flask, in particular, there’re plenty of choices. And in fairness, not all frameworks are created equal. You’ve got flasgger, restx (successor of flask-restplus), flask-RESTful, and flask-smorest, to mention a few. How do you choose among those???

This has talked about in a similar matter: https://github.com/flask-restful/flask-restful/issues/221. However I'm still adamant about just using flask for exception handling. Unless I missed something,I'm having a hard time figuring out how to accomplish this in hopes to get rid of the string concatenation that flask_restful applies to the error message.

Considering the extension you've mentioned explicitly, the author of it has provided an explanation as to why he is not longer putting in any work, you can read about it here.