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
For some reason, celery wouldn't start if I started it first.
Setting paster to start first. Celery starts just fine on initial run
after paster is running.
Added nginx to installation packages. We say that our install uses
nginx, so users should skip nginx if they want to use apache. Also,
our group permissions depend on a web server being installed.
Changed install directory for mediagoblin acct to /var/lib/mediagoblin
It works better if we need to back up data.
Assigned mediagoblin user to the same group as the web server. This
is needed so that the server can access uploaded media.
Created mediagoblin group for non-web-server things such as logs.
Debian-based platforms start the postgres server by default after
installation. For RPM-based distros, we've already issued these
commands prior to configuring the postgres server.
Need to enable / start postgres database on rpm-based distros
before you create the postgres mediagoblin user and database.
If you don't start the database server, you can't create a
database user or database.
The chkconfig command is only needed on CentOS 6, which isn't really
a supported multimedia platform. CentOS 7 and Fedora 21+
wouldn't require this command.
Also made the "exit" command (used after setting up the postgres
mediagoblin account and database) more explicit. This will help prevent
user errors for users who may skim through the documentation.
Some scripts on the internet have referenced paste_local.ini, so
it is safer to have a copy on the filesystem by default, even if
the user doesn't need to change any of the values for a regular
setup.
