flask-static-digest VS flask-pg-extras

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.

You may also want to install this package: https://github.com/nickjj/flask-pg-extras

Flask-PG-Extras for gaining insights on database performance