Closed estevez-dev closed 3 years ago
Does your GitHub token have the necessary scopess in order to create private repositories?
Check your token and whether it has all scopes necessary in order to create, read and write to private repos. Additionally, if the repo CurseforgeBotCache
exists, try stopping the bot, deleting the repository and then starting the bot again.
The logs should then look like this:
Generating new private repository...
Bot-Token is ***
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.
[main] INFO JDA - Login Successful!
[JDA MainWS-ReadThread] INFO WebSocketClient - Connected to WebSocket
[JDA MainWS-ReadThread] INFO JDA - Finished Loading!
Generating cache...
Attempting to save cache...
Pushing to github repo...
Done!
P.S.: If you've created the bot with a specific configuration, then changed the configuration in your docker-compose, you need to delete the config file created by the docker container in your mounted volume. Delete the bot.conf
in said volume and restart the container to generate a new config from the values in your docker-compose.
When using your own Discord bot, make sure you've set the name to what you want it to be in the Discord Developer portal. Personally, I haven't made a lot of experience with using webhooks for Erdbeerbaer's bot, I've always used a Discord bot for that and it happily posts update message under the bots name in my server. So, to directly answer your question: Yes, it is possible, but I don't know how to set it up the way you want using webhooks.
Sorry @Griefed , I posted to the wrong issue ))
The repo was created by a bot, so the permissions are right. I'm running in a Docker container. Here is my Dockerfile:
FROM openjdk
COPY ./Curseforge-Bot-1.2.3.jar /usr/app/
COPY ./bot.conf /usr/app/
WORKDIR /usr/app
ENTRYPOINT ["java", "-jar", "Curseforge-Bot-1.2.3.jar", "-github", "-debug"]
I'm still having [JDA MainWS-WriteThread] INFO WebSocketClient - Connected to WebSocket
as a last log message. Also, there is no bot.conf
created in /config
.
Ah, you're using your own image, that explains why there's nothing in /config. I assumed you were using my image 😅 Hm, sorry, in that case I do not know why the cache is not created in your repository. Strange.
Ah, you're using your own image, that explains why there's nothing in /config. I assumed you were using my image 😅 Hm, sorry, in that case I do not know why the cache is not created in your repository. Strange.
I'll try to use your image
So I used griefed/curseforge-bot:arm
image. bot.conf
is now in /config
, but the last log entry is still:
[JDA MainWS-WriteThread] INFO WebSocketClient - Connected to WebSocket
Ah, one of the older images. Guess DockerHub still keeps those. Please use griefed/curseforge-bot:latest
as every other image can be considered deprecated. The image in latest
is a multi-arch image and works on Raspberry Pis as well (used to run one on my Pi 3B+)
Anyway.
This is such a strange behaviour. I literally have no idea how to adress this. I'm using the latest
image myself on a Linux VPN, with a Discord bot and GitHub cache, and it just works....sorry man, I'm out of ideas.
Umm... Looking at that title, you might have ratelimiting problems. Due to the age of this code I might need to update it so it does not try to cache all members.
For now you should enable Server Members Intent for your bot instances on the discord developers page. Same problem exists for my Discord Integration mod / plugin, but it acutally needs to cache it
Umm... Looking at that title, you might have ratelimiting problems. Due to the age of this code I might need to update it so it does not try to cache all members.
For now you should enable Server Members Intent for your bot instances on the discord developers page. Same problem exists for my Discord Integration mod / plugin, but it acutally needs to cache it
It works, thanks a lot!
So I launched the bot in a Docker container. Here are the logs:
Bot is invited to a server and appears online, but the repository on GitHub is still emapty. Is it intended and the cache will be generated later, or I made something wrong?
My
bot.config
: