Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support monitoring multiple channels in one instance of the script #58

Open
Flynn1111 opened this issue Dec 27, 2022 · 4 comments
Open
Labels
enhancement New feature or request

Comments

@Flynn1111
Copy link

In the interest of archiving all available streams featuring certain channels/people it would be a good idea to allow the script to monitor multiple channels at once without needing a new instance of the script set up for each channel.
the use case would be setting up a regex filter for someone's name and applying it to a list of channels in the event there's an unannounced collab.
as is, i'd have to run a separate script for each friend of the channel i am archiving which can get pretty cluttered.

@glubsy glubsy added the enhancement New feature or request label Dec 28, 2022
@glubsy
Copy link
Owner

glubsy commented Dec 28, 2022

Definitely something I'm considering once I finish rewriting everything async to accomodate this type of use case.

@JunioCalu
Copy link

Has this functionality been implemented yet? The livestream_saver example config file has a lot of monitoring entries so I thought this had been done.

@glubsy
Copy link
Owner

glubsy commented Aug 16, 2023

@JunioCalu you can select one section with the -s argument, but you still need to spawn one python process for each one.

Anyway, lately I have been leaning against implementing this feature, as it is much more error-proof to run one process per channel instead. I also tend to think it would be more manageable when run as a docker image.

@JunioCalu
Copy link

@JunioCalu you can select one section with the -s argument, but you still need to spawn one python process for each one.

Anyway, lately I have been leaning against implementing this feature, as it is much more error-proof to run one process per channel instead. I also tend to think it would be more manageable when run as a docker image.

It is also possible to create multiple instances of livestream_saver using systemd, as in the following examples:

https://stackoverflow.com/questions/48195340/systemd-with-multiple-execstart
https://opensource.com/article/20/12/multiple-service-instances-systemctl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants