This repository was archived by the owner on Jul 14, 2026. It is now read-only.
feat: create_post.py appelle l'API planning au lieu d'envoyer le webhook#28
Merged
Conversation
Termine la partie Web_Planning de UnionRolistes/Bot_Planning_python#11. Le CGI envoyait directement le message Discord via le webhook fourni dans le formulaire, puis tentait (code commenté, jamais fini) de persister dans events.xml via un chemin relatif supposant un système de fichiers partagé avec le bot — incompatible avec des conteneurs séparés. Remplacé par un simple appel POST /events vers la nouvelle API planning (UnionRolistes/Bot_Base #api), qui se charge de l'envoi Discord (via le webhook enregistré par $jdr, retrouvé par user_id) et de la persistance. Plus besoin de discord.py/asyncio ni de connaître le webhook_url côté formulaire : requests suffit.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Réfère UnionRolistes/Bot_Base#79 (nécessite ce service pour fonctionner) et #26 ("move to bot_planing").
Le CGI envoyait directement le message Discord via le webhook fourni dans le formulaire, puis tentait (code commenté, jamais fini) de persister dans
events.xmlvia un chemin relatif supposant un système de fichiers partagé avec le bot.Remplacé par un simple appel
POST /eventsvers la nouvelle API planning, qui se charge de l'envoi Discord (webhook enregistré par$jdr, retrouvé paruser_id) et de la persistance. Plus besoin de discord.py/asyncio côté CGI.