Opened 12 years ago

Closed 7 months ago

#426 closed defect (fixed)

"Separate Celery" section outdated

Reported by: joar Owned by:
Priority: major Milestone:
Component: documentation Keywords: docs bitesized
Cc: Parent Tickets:

Description (last modified by Elrond)

http://docs.mediagoblin.org/siteadmin/production-deployments.html#separate-celery

We now use ./lazycelery.sh, elrond might know more about the intended use of this.

Change History (15)

comment:1 by Christopher Allan Webber, 12 years ago

Milestone: 0.3.00.3.1

comment:2 by Christopher Allan Webber, 12 years ago

Keywords: bitesized added

comment:3 by Christopher Allan Webber, 12 years ago

Owner: somebody removed
Status: newassigned

comment:4 by Christopher Allan Webber, 12 years ago

Keywords: docs, bitesized → docs bitesized

comment:5 by Christopher Allan Webber, 12 years ago

Component: component1documentation

comment:6 by Will Kahn-Greene, 12 years ago

I don't really understand what this bug is about.

Is the text currently in the docs correct?

Is this bug about removing the Separate Celery section or about updating it to some other text?

Joar: If you can give me more direction about what this bug is about, I can work on it for 0.3.2.

comment:7 by Elrond, 11 years ago

Description: modified (diff)
Milestone: 0.3.10.3.4

Updated the main text of the bug to have the correct URL.

Yes, that part of the docs needs to talk about lazycelery.sh.

comment:8 by Elrond, 11 years ago

Cc: Elrond removed
Status: newaccepted

Yes, this is a real bug. Changing to "accepted".

comment:9 by Christopher Allan Webber, 11 years ago

Milestone: 0.4.00.4.1

Moving to 0.4.1

comment:10 by Christopher Allan Webber, 11 years ago

Milestone: 0.5.00.6.0

comment:11 by Christopher Allan Webber, 10 years ago

Milestone: 0.6.00.7.0

comment:12 by Christopher Allan Webber, 10 years ago

Milestone: 0.7.00.8.0

I'm kind of tired of moving around the release milestone on this. I'd like to put it on for 0.8.0, but if we don't get it to then, I'm removing the milestone altogether. We shouldn't be assigning milestones unless we *expect* to complete for them.

comment:13 by Jessica Tallon, 9 years ago

I'm not sure who lazycelery is designed for. If you're hacking on mediagoblin you don't really need it because ./lazyserver handles that for you and if you're deploying for production then you also don't want this as you'd likely want an init script and such and also ./lazystarter always sets CELERY_ALWAYS_EAGER to true even when starting lazycelery so you have all the problems of lazyserver having an always eager celery.

Is someone able to give a use case of this?

comment:14 by Christopher Allan Webber, 9 years ago

Milestone: 0.8.0

comment:15 by Ben Sturmfels, 7 months ago

Resolution: fixed
Status: acceptedclosed

Closing. The documentation on deploying with separate Celery is now pretty thorough.

Note: See TracTickets for help on using tickets.