To adapt to different usages like @wotaniii is doing with his wrapper for #29 we may add an option to configure the secret directory --secret-dir=<path/dir>. Or we can have an option per platform: --secret-youtube=<path/file> and --secret-peertube=<path/file>
To adapt to different usages like @wotaniii is doing with his
[wrapper](https://gitlab.com/juergens/stabbot/blob/4394bde33f0c4e8593425af8c7a32a446a872258/src/peertube.py#L42) for #29 we may add an option to configure the secret directory `--secret-dir=<path/dir>`. Or we can have an option per platform: `--secret-youtube=<path/file>` and `--secret-peertube=<path/file>`
Be careful as Youtube has two files, the youtube-secret and the youtube-credential, it could be confusing. (I have not found solution to merge them unfortunately)
Be careful as Youtube has two files, the youtube-secret and the youtube-credential, it could be confusing. (I have not found solution to merge them unfortunately)
To adapt to different usages like @wotaniii is doing with his
wrapper for #29 we may add an option to configure the secret directory
--secret-dir=<path/dir>
. Or we can have an option per platform:--secret-youtube=<path/file>
and--secret-peertube=<path/file>
Be careful as Youtube has two files, the youtube-secret and the youtube-credential, it could be confusing. (I have not found solution to merge them unfortunately)
I think it is overlapping with #53 and the newer is better (default config file path that can be replaced with symlink and maybe a
--config
option).