No, you can run celery from the same server, the problem is you won't be able to do that on many cheap shared hostings
On Sat, Nov 30, 2013 at 7:35 PM, Robin Lery <[email protected]> wrote: > Thank all so much for you replies. Just one more question though. Does > this means Celery needs a different server? > > > On Sat, Nov 30, 2013 at 12:41 AM, Carlos Daniel Ruvalcaba Valenzuela < > [email protected]> wrote: > >> Signals are like events, for example, when the ORM has done an update. >> Celery is more like a Task queue, you define code to execute certain task, >> load it on celery task server which is running separately from your django >> process, then when you need to execute it in the background you tell it, >> which usually means sending a message through a broker such as redis or >> rabbitmq to the task server, then it gets executed. >> >> Celery is for background tasks, such as processing images, doing updates >> without blocking the main function return, etc. Also celery task can run in >> another machine, while signals are executed locally. >> >> Regards, >> Carlos Ruvalcaba >> >> >> On Fri, Nov 29, 2013 at 11:52 AM, Robin Lery <[email protected]> wrote: >> >>> This may be a lame question, but I am really confused with these two. I >>> know *signals* are used to do some task when something has happened. >>> But what about celery? In the documentation it says: >>> >>> *Celery is an asynchronous task queue/job queue based on distributed >>> message passing.* >>> >>> Will someone please explain to me of what celery is? What's the >>> difference between these two and when to use them? Will be much >>> appreciated! Thank you. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/django-users. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-users/62298d12-02ab-4d34-b8f7-2c4c9bace561%40googlegroups.com >>> . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/CAEF3qbkT2tzvHUcqLsTbg_gxY-%2BtdFinn%2BER5F-PdEf_QV-zHg%40mail.gmail.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CA%2B4-nGqoCrLoc7BY0Le-7izz7w0qO9-LWWzMZixjWPt5_ZGqCw%40mail.gmail.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFWa6tL29fSivUpzoT-cYL2qQDFj%2Bv5gmepEN%3DWF0du8SJaJSA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
