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.
In addition to side-stepping spectrograms completely in Python 3 in 1038aea8,
this commit adds some fallbacks that will help with potential issues in Python 2.
Fixes Issue #5457
Signed-off-by: Ben Sturmfels <ben@sturm.com.au>
Author: Jorge <mediagoblin@gybs.waa>
Make the batchaddmedia command look for a 'collection-slug' column, that
for each row may specify the slug of a collection that the media should
be added to. This matches the '--collection-slug' argument of the
addmedia command.
Commit c0ea2bad changed the expected location column header of csv files
used by the batchaddmedia command from 'media:location' to 'location'.
This change updates the docs to match.
* docs/source/siteadmin/plugins.rst:
Added a reminder to run "./bin/gmg dbupdate" after installing a plugin.
Added a new "Deactivating plugins" section.
Renamed "Removing plugins" to "Removing plugin packages".
Things have gotten both easier and more complex in the branching world
view. Plugins branch off of main with their own migrations.
Generating these has become a bit easier, but the steps for doing this
are a bit wordy to explain.
* docs/source/pluginwriter/database.rst: Update both the
"Creating new Tables" and "Changing the Database Schema Later"
sections accordingly.
The user_dev directory gets created when users get established
and they start uploading media. However, the permissions aren't
correct on the directory as it gets created.
As a workaround, we create the directory at this stage, and then
set the proper permissions.
See this mailing list post for more information:
http://lists.mediagoblin.org/pipermail/devel/2015-May/001201.html
