pymoof VS celery

I'm not sure if it will work with a firmware above 1.8.0 as there seem to be [issues with that version](https://github.com/quantsini/pymoof/issues/7) tough i cannot verify it as i'm below that version.

If not, It's still possible with pymoof , vanbike-lib or Moofer

There is no .apk as far as i know. If you want to change the settings like region settings or assist, use pymoof or vanbike-lib

The only real third-party app is Moofer. Costs 10 bucks and you can manipulate the region setting and a few other things. Doesn't work as good on Android as on iOS and isn't truly necessary for riding. It's cool though. Vanmoof say it will void your warranty though. If you want to save 10$, experiment a bit and change things you could also use pymoof. It's not an app though and more for Pro's. Personally, I only use the official app or pymoof if I want to experiment.

Or If you're cheap and want to save 10 bucks, try pymoof

Yes, moofer (and every other third party tool like pymoof or vanbike-lib ) can still set the region to US, but not in offroad mode (38km/h or assist level 5)

So this might be my understanding, but stuff like celery is more like an orchestrator that chunks up workloads (think Hadoop with multiple nodes).

In the Django world, you'd probably rely on Celery to do this for you. You're probably looking for something similar that works with Go. https://github.com/celery/celery

I've been doing some research and there doesn't seem to be much information on this issue, aditionally there's this but without a fix yet or any workaround: https://github.com/celery/celery/issues/7792

RabbitMQ Classic mirror queues are very fragile to network partitioning. They are deprecated in favor of Quorum queues, but Celery doesn't support them yet : https://github.com/celery/celery/issues/6067

The Celery package provides some number of (undocumented!) result backends to store task results in different local, network, and cloud storages. The django-celery-result package adds options to use Django-specific ORM-based result storage, as well as Django-specific cache subsystem.

I spent 3 years building a high scale crawler on top of Celery.

I can't recommend it. We found many bugs in the more advanced features of Celery (like Canvas) we also ran into some really weird issues like tasks getting duplicated for no reason [1].

The most concerning problem is that the project was abandoned. The original creator is not working on it anymore and all issues that we raised were ignored. We had to fork the project and apply our own fixes to it. This was 4 years ago so maybe things improved since them.

Celery is also extremely complex.

I would recommend https://dramatiq.io/ instead.

[1]: https://github.com/celery/celery/issues/4426

You can use celery to process the file for extraction, saving and creating rar/zip.

Celery not usefull for long term future tasks (far future) · Issue #4522 · celery/celery (github.com)