Hi! I took a look at this.
Could you please clarify what your main goal is with the bot? Running the full MonitoRSS suite on Koyeb isnāt really possible (as far as I know) due to resource limits~, especially on the free tier [not correct]. But Iām curious to hear what you have in mind!
(e.g. if you just want a Discord bot and not specifically from MonitoRSS you could try using a different way, like discord.py. If thereās a specific feature from MonitoRSS you want, just tell me and Iāll try to find an alternative for it.)
Here is how to set up a minimal bot using MonitoRSS.
Go to Koyeb, and click Create Service
Select Docker (not Github)
Set the Image to synzen/monitorss:latest, leave Registry empy.
In the environment variables set these: DRSS_BOT_TOKEN = BOT TOKEN HERE DRSS_DATABASE_URI = MONGODB LINK HERE DRSS_START = bot ā donāt change this one FEED_REQUESTS_FEED_REQUEST_DEFAULT_USER_AGENT = MonitoRSS/1.0 your@email.com
Now click deploy and youāre done!
Your bot should be online, and you can set it up further how you like.
The issue is that that is the old version of MonitoRSS, which has several problems, such as sending duplicate articles and sometimes not sending articles at all. Thatās why this version is now deprecated in favor of the new one that uses Docker Compose.
I want to use the updated version of MonitoRSS, not the old one that has many serious issues.
I have sensitive data, like a Discord token, which I cannot make public. Thatās why I created a private repo. The only difference between github .com/sn-o-w/MonitoRSS and the private repo is that I renamed .env.example to .env.prod and I added all the environment variables to file .env.prod.
How did you get the docker compose working? Simply using the Dockerfile.koyeb in your repository doesnāt seem to work for meā¦
No kernel access
=== Unable to start docker daemon ===
Certificate request self-signature ok
subject=CN = docker:dind server
/certs/server/cert.pem: OK
Certificate request self-signature ok
subject=CN = docker:dind client
/certs/client/cert.pem: OK
ip: can't find device 'nf_tables'
lsmod: /proc/modules: No such file or directory
modprobe: can't change directory to '/lib/modules': No such file or directory
ip: can't find device 'ip_tables'
lsmod: /proc/modules: No such file or directory
modprobe: can't change directory to '/lib/modules': No such file or directory
mount: permission denied (are you root?)
Thanks, that worked for me!
I think the issue is that something is wrong in the setup, Iām getting the standard āTCP health check failed on port 8000.ā and then my instance is killed. Iāve tried multiple changes in both the build command and the source files but I sadly couldnāt find a solution for this. Perhaps someone more experienced with Dockerfile should look into thisā¦