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.
This fixes the installation process *right now* on Python 2. The problem is that
packages are dropping Python 2 support all over the place and due to
our (deliberate) loose dependency version specifications and the loose
sub-dependency version specifications, it's one horrible mess. But it works
right now.
Next up I'll be pinning all the currently installed Python 2 packages and all
dependencies.
Mostly a thorough test and cleanup. The significant change is moving the systemd
config into the deployment docs an the registration/security considerations to
production considerations docs.
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/.
flup is not supported on Python3, so MediaGoblin doesn't have a supported way to enable FastCGI support.
This change removes all references to flup and FastCGI and updates deployment instructions to use simple HTTP forwarding with nginx to access mediagoblin's non-static resources.
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.
