Soft decoupling of site and bot about bot HOT 6 CLOSED

Comment from Leon Sandøy:

after we do https://gitlab.com/python-discord/projects/site/issues/45 we don't even need rabbitmq.

from bot.

This might be better as a project.

from bot.

At some point today I’m going to draft up a broader discussion issue on separating out some of the core functionality to better support multiple bots, development, security/redundancy, etc. that this would likely fall under. The scope is definitely large enough to be a project rather then a single issue.

from bot.

I've created a new org-level project for you to track this. Let me know if you need a hand with it.

from bot.

This issue is quite stale. @lemonsaurus can you give an update on what you think we should still go for?

from bot.

If I'm correctly interpreting the intent of this issue as alleviating pains for local dev, I think the functionalilty introduced by #444 meets the spirit of this issue.

With this repository now providing the postgres backend via docker-compose, contributors are able to competently work on the bot solely from its own repo. As far as I can tell this provides a viable cross-platform experience with minimal additional setup (e.g. getting the bot token from the API) and no reliance on getting the site repo up and running.

As an added bonus, once the user's environment is properly configured (docker installed, hosts set up), they can make the jump to developing with site & bot as separate entities with essentially no additional effort.

from bot.