| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
|
|
|
|
|
|
| |
Includes "home", "collection", "view all user's media" and "user's profile" views.
Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
|
| |
|
|
|
|
| |
This help a Guix package to locate the basic static assets.
|
|
|
|
|
|
|
| |
There was an existing stub for `gmg serve`, but had never been completed.
This will make it simpler to run the MediaGoblin web interface and media
processing backend.
|
|
|
|
|
|
|
| |
Turns out this breaks tests. Will attempt again when I have time to deal with
the tests.
This reverts commit 120f144f0eb014e694a584a627c8b17856da5b51.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this change, the Celery logging did not include any of the logging
calls within MediaGoblin because `disable_existing_loggers` defaulted to True.
This was unhelpful and inconsistent with the logging behaviour of the web process.
The MediaGoblin web process sets logging output based on the configuration in
paste.ini. This is loaded by the `paster` program, rather than MediaGoblin
itself.
The MediaGoblin celery process manually loads its logging config from paste.ini,
but previously defaulted to `disable_existing_loggers=True`, meaning that none
of the application logging flowed through unless the logger was explicitly added
to paste.ini.
|
|
|
|
|
|
|
|
|
|
| |
Following the video transcoding work included in v0.10.0, uploading an image and
restarting Celery resulted in the image being marked as failed, even after it
had been initially successfully processed.
The issue was that the initial processing task was not being acknowledged by the task queue following the introduction of the
`CELERY_ACKS_LATE` setting. It's not clear why this is the case, but reverting
the setting fixes this issue and doesn't negatively impact video processing.
|
|
|
|
| |
Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Mozilla persona is RIP since 2016.
Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
|
| |
|
| |
|
|
|
|
|
|
|
| |
This button just uses JavaScript to reveal the subsequent actions. Better to
show these upfront.
Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Olivier Mehani <shtrom+mediagoblin@ssji.net>
|
| |
|
|
|
|
| |
video [#5589].
|
| |
|
|
|
|
|
| |
This change gives a clean test run in the Debian-based Python 2 and Python 3
docker images.
|
|
|
|
| |
This reverts commit 2b487fc16de2fc7c961f8df725c5ece0e5f56e3a.
|
|
|
|
| |
This reverts commit f1c288b1d87fed959a124816ef7a8fd40aec3dd3.
|
|
|
|
|
|
| |
For 0.10.0 we're removing specrograms entirely for reliability. This change only
disables spectrograms and updates install docs and Dockerfiles. We still need
to strip out all the spectrogram code and extlib/freesound/.
|
| |
|
|
|
|
| |
Fixes #5590.
|
|
|
|
|
|
|
|
|
|
| |
Prior to this change, when pagination kicks in on the user management or report
management panel, the following exception is raised:
TypeError: a bytes-like object is required, not 'str'
The cause is that `request.query_string` in the URL parameters in raw bytestring
form as per Werkzeug documentation.
|
|
|
|
| |
This reverts commit b6fba854007bb4392846085a60178c44dbd7989e.
|
|
|
|
|
|
|
|
|
|
|
| |
This doesn't seem to be an issue in my Guix SD/Python 3.7 testing, but hit an
issue on Debian 9/Python3.5 where concatenating text to `request.query_string`
was causing the error:
TypeError: a bytes-like object is required, not 'str'
This clearly hasn't been an issue in the past though, so I suspect there's a
library somewhere that's on a different version and is behaving differently.
|
|
|
|
| |
Unfortunately now the player isn't showing up because there's no thumbnail.
|
| |
|