wsdd VS celery

https://github.com/christgau/wsdd/blob/master/README.md https://bugzilla.samba.org/show\_bug.cgi?id=11473

`--net=host` will connect container to hosts stack (it becomes hosts). without it container connects to `bride` network thus requiring exclusive port forward. See wsdd section firewall setup and you may like to revist following

You can install this on your RPi to be able to discover them: https://github.com/christgau/wsdd

Windows stopped using NetBIOS ever since they deprecated SMB1. It uses Web Service Dynamic Discovery (WS-Discovery). If your server is running Linux, you can install a 3rd party daemon to add WS-Discovery support. See here for more background.

Microsoft changed* how SMB network discovery works. To get my Raspberry Pi running RasPiOS to show up on the network I have to install the Windows Network Discovery Daemon

That's interesting although I'm not a Mac user OMV uses wsdd and has therefore made things easier on a windows network. I think, but I can't confirm you can deploy wsdd on a Mac would that solve it......just a thought

If you check out the WSDD python script in the askubuntu link ( https://github.com/christgau/wsdd ) it can make the samba server visible in "network".

Install wsdd on the Pi - https://github.com/christgau/wsdd

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)