Issue is that Werkzeug > 1.0.0 has removed werkzeug.contrib.atom.AtomFeed,
making it difficult to use a distribution-packaged version of werkzeug. To solve
this, I've replaced use of werkzeug.contrib.atom.AtomFeed with
feedgenerator.Atom1Feed.
After the change, the only major difference between the feeds before and after is
that they use <summary> instead of <content>. Minor differences include no longer
adding 'type="text/html"' on some <link> elements and no "xml:base" attribute on
<entry> elements. I don't think these differences will have any noticable
effect.
Tested on Liferea feed reader.
We may need to push download link creation into the view in the future to make
it more fully featured, but this will solve the immediate issue with missing
download links on new media after 0.10.0. Sorting of entries won't be right if
your media is over 999p since it's alphabetical.
Previously had partial docs for Fedora 31. This updates to Fedora 33, adds
support for audio and video and adds dependencies to allow the test suite to run
to completion.
The latest version is 1.4.0b1 which changes some internals a bit... internals
which unforuntately mediagoblin's DatabaseManager screw around with
(namely, _decl_class_registry)
Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
The `audiotospectrogram` module is a complete rewrite of the existing spectrogram
code with support for Python 3. This allows us to drop the bundled `freesound`
library and Python 2-only `audioprocessing` and `spectrogram` modules.
Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
A trailing slash in devtools/compile_translations.sh caused that script to fail
because the parameter to pybabel's -l option ended up blank instead of
containing the language code.
A few files and directories were missing from .gitignore and hence wound up
in the list of local changes to be committed.
By increasing the limit from 8m to 100m, we should immediately fix initial
problems for people trying to upload audio or video. From there, they can read
the documentation more closely when they try to upload larger files.
This change starts Celery only after RabbitMQ is available. It also returns the
unnecessarily low BROKER_HEARTBEAT setting to default of 120.0 to help prevent
connections being reset on machines under load.