As Elrond suggested, MEDIA_MANAGER for all the media types must point to the new MediaManager classes. Currently, this is enabled only for "Image" media type. The attached patch makes MEDIA_MANAGER point to a class derived from MediaManagerBase for all the other media types. I have tested it manually for all the media types.

In the ​Considerations for Production Deployments, there are a few distribution specific init scripts mentionned. Here's a more cross-system one, using Supervisor, a process control system. On Debian, it's more reliable than ​joar's MediaGoblin init scripts, as it doesn't fail at restarting them.

I suggest to add the following "init method" for Debian in the documentation mentionned above.

The Paster FCGI server supervisor file, with MediaGoblin's documentation paths.

[program:mediagoblin-paster]
command = /srv/mediagoblin.example.org/mediagoblin/bin/paster serve /srv/mediagoblin.example.org/mediagoblin/paste_local.ini --server-name=fcgi fcgi_host=127.0.0.1 fcgi_port=26543
directory = /srv/mediagoblin.example.org/mediagoblin
user = mediagoblin
autostart = true
autorestart = true
stdout_logfile = /var/log/supervisor/mediagoblin-paster.log
stderr_logfile = /var/log/supervisor/mediagoblin-paster_err.log
environment = CELERY_ALWAYS_EAGER=false

The Celery task processor supervisor file, with MediaGoblin's documentation paths.

[program:mediagoblin-celeryd]
command = /srv/mediagoblin.example.org/mediagoblin/bin/celeryd
directory = /srv/mediagoblin.example.org/mediagoblin
user = mediagoblin
autostart = true
autorestart = true
stdout_logfile = /var/log/supervisor/mediagoblin-celeryd.log
stderr_logfile = /var/log/supervisor/mediagoblin-celeryd_err.log
environment = CELERY_CONFIG_MODULE="mediagoblin.init.celery.from_celery"

I'm not a supervisor-guru, I just followed these ​Section Values in supervisor's configuration documentation, so anyone is free to improve it, of course !

Hello, I read about the Mylar platform on Slashdot.org <​http://yro.slashdot.org/story/14/03/26/0352201/mit-researchers-create-platform-to-build-secure-web-apps-that-never-leak-data>. It is built on the Meteor framework and decrypts user data only in the browser, even website administrators cannot see what the user has on their account.

The developers of Mylar, who also helped develop CryptoDB, have already made an instant messaging application based on it which could be easily integrated into MediaGoblin for social networking features since it is already built. Even converting MediaGoblin to the Mylar platform might be easy since the Mylar developers only had to change about 35 lines of code for the applications they have already converted to Mylar.

But, I guess the ease of the MediaGoblin's transition to Mylar depends on whether MediaGoblin is written in Javascript or not since Mylar application are entirely written in Javascript (no MySQL or any other server side code, but I think CSS is still used). I tried to check the repository for MediaGoblin to make sure it is already using some Javascript, but Gitorious doesn't show the language statistics for the repository like it would on Github.

Let me know what you think, Here's Mylar's website on MIT servers <​http://css.csail.mit.edu/mylar/>.