Opened 15 years ago

Closed 14 years ago

#214 closed defect (fixed)

Switch celery keys to be all-uppercase

Reported by: Christopher Allan Webber Owned by: Larisa Hoffenbecker
Priority: minor Milestone:
Component: programming Keywords: bitesized
Cc: Parent Tickets:

Description (last modified by Christopher Allan Webber)

Celery will finally be moving to a structure that will be much, much easier for combining with MediaGoblin. Horray!

http://ask.github.com/celery/internals/app-overview.html

In order to better prepare for this, we should switch our config system setup for celery's configuration to also have all celery-relevant keys to be ALL_UPPERCASE in form.

So a few changes:

  • Update mediagoblin/config_spec.ini and set all keys to UPPERCASE form.
  • Update mediagoblin/init/celery/init..py 's setup_celery_from_config and remove the force-to-upper... well maybe anyway! I suppose it doesn't hurt to include this, but it isn't necessary any more.

This is a simple, bitesized task, appropriate for a new contributor.

Change History (10)

comment:1 by Christopher Allan Webber, 15 years ago

Milestone: 0.1.0
Owner: set to Larisa Hoffenbecker

comment:2 by Christopher Allan Webber, 15 years ago

Milestone: 0.1.00.2.0

comment:3 by Christopher Allan Webber, 15 years ago

Milestone: 0.2.00.2.1

comment:1 by Will Kahn-Greene, 14 years ago

The original url for this bug was http://bugs.foocorp.net/issues/509 .

comment:2 by Christopher Allan Webber, 14 years ago

Keywords: bitesized added

comment:3 by Christopher Allan Webber, 14 years ago

This shouldn't take too much effort, and we really should get it in before anyone starts doing anything complex with their celery setups.

comment:4 by Christopher Allan Webber, 14 years ago

Larisa says she'll be busy for the next 2 weeks, so if someone wants to take this over they can jump on it.

comment:5 by Elrond, 14 years ago

Milestone: 0.2.1

comment:7 by Christopher Allan Webber, 14 years ago

Description: modified (diff)
Resolution: fixed
Status: acceptedclosed

Merged!

Note: See TracTickets for help on using tickets.