alfem/telegram-download-daemon

Docker

Closed this issue · 10 comments

baruchiro commented

We need to put this deamon in Docker Image and publish it with Github Actions

baruchiro commented

So I created a Dockerfile in #9.

But I have a problem, related to the two-factor authentication situation. The TelegramClient constructor request us to insert our phone number in the console, and then insert the security code we received from Telegram.

This authentication not required after the first time I run the script, so I need to do research about that, if and how we can solve this problem.

mitto98 commented

I've created the repository (https://hub.docker.com/repository/docker/mitto98/telegram-download-daemon), let me know when you have finished, so I can build and push it.

baruchiro commented

@mitto98 I think you actually publish the image now, but you can see in the comment above that I have a problem.

Also, I will want to create a Github Action for CD the image, so when I will implement that, you will need to share a secret or something with @alfem

baruchiro commented

I don't have a Telegram experience, and I have very little experience with Docker, so I went to a gamification solution: https://stackoverflow.com/questions/61395907/telethon-telegramclient-authentication-in-docker-container

When you give points to people, they will want to answer you even if your project is not in their best interest.

alfem commented

I wonder why the question in stackoverflow had -1 points. I have given it +1.

I also wonder why are you so interested in this script, but that is another issue :-D

baruchiro commented

Thanks @alfem !

I'm interesting this script because I want to create a docker-composr for my home-server.

I'm thinking about docker for Plex, and I need another docker for downloading content to the Plex folder. And because I often get content to watch from Telegram, I'm looking for a way to download automatically.

  • 👍1
baruchiro commented

Hi @alfem , currently I'm using the docker from my fork, with a GitHub Docker Registry.

I don't like to work with forks, of course I think all the forks should update the original repo for keep it updated with all problems solved in the forks.

But if you feel I'm moving too fast, that's fine.

I just want to say that I will continue to maintain my fork, and you will have to see if I have solved any problems there, you will need to merge them to this repo.

Also I think I will create my own image in DockerHub

alfem commented

Thanks for asking!
I had a severe failure in my laptop and got it fixed a couple of days ago (new hd, new motherboard...).

I am fine with your fork, as I trust your work with the docker issues. Just remember to throw me a pull request when it got ready.

baruchiro commented

Pull Request #9 is about this issue.

alfem commented

Oops, I see. I thought you were still working out the auth mechanism.

Please, check my comments in #9 and I will merge it ASAP