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

Config.yaml not allowing multiple groups? #13

Closed
BradKML opened this issue May 12, 2021 · 3 comments
Closed

Config.yaml not allowing multiple groups? #13

BradKML opened this issue May 12, 2021 · 3 comments

Comments

@BradKML
Copy link

BradKML commented May 12, 2021

When loading the app, group: "your_group_name" is the default, it seems that that the software did not make a note on archiving multiple groups or channels.

@knadh
Copy link
Owner

knadh commented May 12, 2021

If you have multiple groups, you should create multiple config's for each group. eg: mygroup.yaml, mygroup2.yaml.

Don't forget to use different directories for storing media for different groups (media_dir) across these config files, and also use a different data file for each group when calling tg-archive --data.

@knadh knadh closed this as completed May 12, 2021
@BradKML
Copy link
Author

BradKML commented May 12, 2021

@knadh it might sound weird to be asking for a generator that can spawn these en masse. Also, imagine launching them in parallel... would be painful for the ports/RAM.

@knadh
Copy link
Owner

knadh commented May 14, 2021

This can be done easily with some external scripting. Doesn't make sense to add config template generation to the core.

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

No branches or pull requests

2 participants