pyres

There were so many corpses they had to exhume their mass graves and burn bodies on pyres.

They also split the web interface (resweb) into a separate project, so pyres doesn't depend on a web framework now.

When all of the dead become part of the army of the white walkers, people will start accepting funeral pyres again.

The pyres web interface (where you can view job status) is built using itty.

There's also the question of the true cost of all the hardware, electricity, and potential output that's being tossed onto the pyres.

Someone will read as moral that the people of Rome or Warsaw haggle, laugh, make love as they pass by the martyrs' pyres.

Thanks for the suggestion, I'll check pyres out when I get to that point in my project.

Pinterest replaced Celery and RabbitMQ [1] with their fork of pyres [2], presumably because it's 1/100th the codebase but does what they need to.

Kue is similar to ruby's resque or python's pyres so the advantage was that every request was basically an independent job using redis as a pubsub.

Maybe a hundred million funeral pyres and a desert of glass will be a monument large enough that we’ll never forget again.

It's modern book burning, just less dramatic without the pyres.

Research the censorship laws in the century prior to the Statute of Anne, and the burnings in St James' Square where 'unauthorised' publishers were immolated on pyres of their own books.

We used to burn the printers of "seditious works" on pyres of their own books in St James' square in London.

"Making this bread really takes me back to growing up with the funerary pyres at Grandma's house"

They lacked reason, souls, and were only automata, after all: "It was a form of medieval French entertainment that, depending on the region, involved cats suspended over wood pyres, set in wicker cages, or strung from maypoles and then set alight.

Pyres looks like a good alternative for Celery in the Python world when you don't need Celery's cron-like features.