Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wsgi #1

Open
KrisBuytaert opened this issue Dec 14, 2011 · 3 comments
Open

wsgi #1

KrisBuytaert opened this issue Dec 14, 2011 · 3 comments

Comments

@KrisBuytaert
Copy link

Any docs on getting it to run from apache .

Or a Sponge.settings available ?

@stpierre
Copy link
Owner

Kris--

Not yet. I'm working on it, but the Celery packages for RHEL 6 are
really crap, so there's lots of random stuff you have to do to get
celeryd and celerybeat running as standalone daemons. Rough outline:

  1. Grab the init scripts at liked to from
    http://ask.github.com/celery/cookbook/daemonizing.html for celeryd and
    celerybeat.
  2. Create a "celery" user and group.
  3. Create /var/log/celery and /var/run/celery; make them owned by the
    celery user/group and perms 0755.
  4. Configure /etc/sysconfig/celerybeat and /etc/sysconfig/celeryd.
    You can find outlines of those at
    http://docs.celeryq.org/en/latest/cookbook/daemonizing.html#init-script-celerybeat
    There aren't a ton of surprises in there, but make sure you have
    CELERYBEAT_OPTS="-S djcelery.schedulers.DatabaseScheduler" in
    /etc/sysconfig/celerybeat
  5. In RHEL 6, the celery egg has what appears to me to be a bogus
    requirement on python-dateutil >= 1.5.0; you may have to edit
    /usr/lib/python2.6/site-packages/celery-2.2.7-py2.6.egg-info/requires.txt
    and change that line to python-dateutil>=1.5.0,<2.0.0
  6. Create ~apache/.pulp, owned by apache with permissions 0755.
  7. Start the celeryd, celerybeat, and rabbitmq-server services and
    restart httpd.

I use the settings.py included with Sponge almost completely
unmodified to run under Apache. Certainly there's nothing in there
that would cause problems.

Hopefully that gets you started; I'll try to get a more complete
writeup done some time this week. Glad you're interested! :D

On Wed, Dec 14, 2011 at 6:15 AM, Kris Buytaert
reply@reply.github.com
wrote:

Any docs on getting it to run from apache .

Or a Sponge.settings available ?


Reply to this email directly or view it on GitHub:
#1

Chris St. Pierre

@stpierre
Copy link
Owner

Kris--

I found some time today to write up some better docs:

https://github.com/stpierre/sponge/blob/master/README.apache

These are mostly untested; I just reverse engineered what I've got in
Bcfg2. YMMV, but feedback is very welcome. :)

Thanks!

On Wed, Dec 14, 2011 at 7:50 AM, Chris St. Pierre
chris.a.st.pierre@gmail.com wrote:

Kris--

Not yet.  I'm working on it, but the Celery packages for RHEL 6 are
really crap, so there's lots of random stuff you have to do to get
celeryd and celerybeat running as standalone daemons.  Rough outline:

  1.  Grab the init scripts at liked to from
    http://ask.github.com/celery/cookbook/daemonizing.html for celeryd and
    celerybeat.
  2.  Create a "celery" user and group.
  3.  Create /var/log/celery and /var/run/celery; make them owned by the
    celery user/group and perms 0755.
  4.  Configure /etc/sysconfig/celerybeat and /etc/sysconfig/celeryd.
    You can find outlines of those at
    http://docs.celeryq.org/en/latest/cookbook/daemonizing.html#init-script-celerybeat
     There aren't a ton of surprises in there, but make sure you have
    CELERYBEAT_OPTS="-S djcelery.schedulers.DatabaseScheduler" in
    /etc/sysconfig/celerybeat
  5.  In RHEL 6, the celery egg has what appears to me to be a bogus
    requirement on python-dateutil >= 1.5.0; you may have to edit
    /usr/lib/python2.6/site-packages/celery-2.2.7-py2.6.egg-info/requires.txt
    and change that line to python-dateutil>=1.5.0,<2.0.0
  6.  Create ~apache/.pulp, owned by apache with permissions 0755.
  7.  Start the celeryd, celerybeat, and rabbitmq-server services and
    restart httpd.

I use the settings.py included with Sponge almost completely
unmodified to run under Apache.  Certainly there's nothing in there
that would cause problems.

Hopefully that gets you started; I'll try to get a more complete
writeup done some time this week.  Glad you're interested! :D

On Wed, Dec 14, 2011 at 6:15 AM, Kris Buytaert
reply@reply.github.com
wrote:

Any docs on getting it to run from apache .

Or a Sponge.settings available ?


Reply to this email directly or view it on GitHub:
#1

Chris St. Pierre

Chris St. Pierre

@KrisBuytaert
Copy link
Author

On Wed, 2011-12-14 at 10:51 -0800, Chris St. Pierre wrote:

Kris--

I found some time today to write up some better docs:

https://github.com/stpierre/sponge/blob/master/README.apache

I think one of the first things you wrote was

"
You must run Sponge on a different server than Pulp; a WSGI wizard
might be able to get them both running on the same box, but that
wizard ain't me.
"

I`m going to try that first before I dig into Celery and stuff :)

greetings & thnx

Kris

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants