Custom Query (1173 matches)
Results (196 - 198 of 1173)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #492 | fixed | comment preview | ||
| Description |
Given that comments use a markup, it'd help a lot to have comment preview. I've seen this work in a few ways on the internet. Trac shows you the preview while you're writing the comment in a different box. I like that--it's pretty helpful. MediaWiki has a "preview" button and shows you what it'll look like when it's posted. Pyblosxom works this way, too. This works, but it's far less convenient. I'd prefer us to implement the first. Maybe use AJAX to round-trip formatting the comment to get the preview every few seconds? Is that safe? |
|||
| #732 | fixed | celeryconfig module not found when running dbupdate | ||
| Description |
When I'm running "./bin/gmg dbupdate" I'm getting this warning, which apparently isn't fatal, but a bit scary and annoying :-) According to joar it's because it is run without CELERY_CONFIG_MODULE being set. /var/www/media/local/lib/python2.7/site-packages/celery-2.5.3-py2.7.egg/celery/loaders/default.py:64: NotConfigured: No 'celeryconfig' module found! Please make sure it exists and is available to Python. "is available to Python." % (configname, ))) |
|||
| #5520 | no-action | celery has wrong broker in config files | ||
| Description |
After installing mediagoblin and used the systemd init files, I wasn't able to transcode any files.. After checking the logs /var/log/messages I get the following error: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused. Trying again in 14.00 seconds... [2017-07-28 17:39:06,874: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused. Trying again in 16.00 seconds... [2017-07-28 17:39:22,912: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused. Trying again in 18.00 seconds. After searching through the issues, I found issue #859: https://issues.mediagoblin.org/ticket/859 somewhat related to this problem... I've checked config_spec.ini and found this: [celery] # default result stuff CELERY_RESULT_BACKEND = string(default="database") CELERY_RESULT_DBURI = string(default="sqlite:///%(here)s/celery.db") # default kombu stuff BROKER_URL = string(default="amqp://") After changing the kombu stuff to: BROKER_TRANSPORT = string(default="sqlalchemy") BROKER_URL = string(default="sqlite:///%(here)s/kombu.db") now it works... I've never touched this file, this is configuration by default and there's nothing in the easy deployment wiki page to change something in here... |
|||
