-- BotBot disconnected, possible missing messages --
-- BotBot disconnected, possible missing messages --
-- BotBot disconnected, possible missing messages --
[o__o] joined the channel
alanjds[m] has quit
atrosh[m] has quit
lavalamp joined the channel
lavalamp has quit
d-fence has quit
hphuoc25 joined the channel
d-fence_ joined the channel
subho joined the channel
hphuoc25 has quit
hphuoc25 joined the channel
hphuoc25 has quit
atomekk joined the channel
hphuoc25 joined the channel
hphuoc25 has quit
hphuoc25 joined the channel
hphuoc25 has quit
hphuoc25 joined the channel
subho_ joined the channel
subho has quit
subho_ has quit
subho joined the channel
subho has quit
subho joined the channel
hphuoc25 has quit
subho has quit
hphuoc25 joined the channel
subho joined the channel
hphuoc25 has quit
hphuoc25 joined the channel
Ergo joined the channel
subho has quit
atrosh[m] joined the channel
hphuoc25 has quit
hphuoc25 joined the channel
palkeo[m] joined the channel
alanjds[m] joined the channel
czart__ joined the channel
subho joined the channel
alanjds[m] has quit
atrosh[m] has quit
palkeo[m] has quit
F2_ joined the channel
subho has quit
atrosh[m] joined the channel
subho joined the channel
hphuoc25 has quit
hphuoc25 joined the channel
hphuoc25 has quit
deb joined the channel
deb is now known as Guest53888
Guest53888
how to know if celery task has fininshed?
Guest53888 has quit
subho has quit
hphuoc25 joined the channel
hphuoc25 has quit
alanjds[m] joined the channel
palkeo[m] joined the channel
inovas_ joined the channel
atomekk joined the channel
clokep joined the channel
subho joined the channel
F2_ has quit
subho has quit
atomekk joined the channel
atomekk has quit
atomekk joined the channel
subho joined the channel
m27 joined the channel
jdickers joined the channel
m27
I'm thinking about running my complete python/celery app in docker. I have very limited experience with docker. Is Docker and Celery a good fit? Im worried that reading logfiles might be a problem. (also; I cant use supervisor to make sure celery is running)
josuebc
m27: I've run Celery with docker and is pretty easy to do. Log files shouldn't be a problem. You can write to anything/anywhere you want by configuring your logger correctly.
There are docker logs, but those are more about what's going on on the container. For applications running in the container you could either just log everything to stdout/stderr and see those logs with journalctl or syslog.
If you can't use supervisord then I would suggest to run one worker per container and use docker-compose.
Then, you can set auto restart on your docker-compose.yml file. So, if a worker fails docker-compose will automatically restart that container.
inovas_ has quit
inovas_ joined the channel
niska joined the channel
subho has quit
hphuoc25 joined the channel
F2_ joined the channel
hphuoc25 has quit
m27
Thanks for laying out how to set up Docker and celery!
If I understand you correctly, it's actually quite simple. Run the celery worker as a 'front process', and monitor the STDOUT.
subho joined the channel
jarthur joined the channel
lavalamp joined the channel
josuebc
m27: Exactly. That way nothign is "docker specific" and your setup is somewhat docker (or other like that) agnostic. I mean, as much as one can do that.
cyp3d joined the channel
jarthur has quit
subho has quit
subho joined the channel
sash_ has quit
sash_ joined the channel
subho_ joined the channel
subho has quit
jarthur joined the channel
lavalamp has quit
lavalamp joined the channel
inovas_ has quit
fission6 joined the channel
mush joined the channel
mush
so we're having a discussion at work about why celery was named celery, does anyone know the history?
josuebc
mush: Ah, good question. I have no idea haha
mush
I want to say its because of rabbitmq.
and rabbits eat celery.
Getting push back cause folks are saying they should have named it `carrot`.
hphuoc25 joined the channel
josuebc
mush: That's a good guess. Although looking at the initial commit it used to be called "crunchy" so maybe it has to do with rabbit and then something else happened?
mush: Wait, there is a reference to a carrot package
So, that's probably on point
hphuoc25 has quit
Also I thikn celery was first developed for Django only. So that makes sense. Ask Solem probably couldn't name it carrot because there was already a carrot package so he went for something "crunchy" until eventually celery.