Don't over complicate this. Use a single container that runs the bot and can write to a host directory. Have the bot run yt-dlp whenever it finds a youtube link and download to the host directory. For moving the videos based on size you can write code in the bot to do it after download, or you can run a cron job to do it (either in the container or on the host), or maybe yt-dlp has an option for that.
this post was submitted on 31 Oct 2023
1 points (100.0% liked)
Self-Hosted Main
511 readers
1 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
For Example
- Service: Dropbox - Alternative: Nextcloud
- Service: Google Reader - Alternative: Tiny Tiny RSS
- Service: Blogger - Alternative: WordPress
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.
Useful Lists
- Awesome-Selfhosted List of Software
- Awesome-Sysadmin List of Software
founded 1 year ago
MODERATORS
I have a series of containers that use the host network and share messages over MQTT. Works well. One of them launches other containers when specific trigger phrases are said in specific topics. Another one sends trigger phrases based on a schedule.
Just use docker-compose? Put multiple containers in one compose file. Create an internal network for them to communicate with.
As far as the general solution to the higher level question asked, this is the way. For the specific application, can certainly question the question of the multiple containers in the first place.
why not just use redis