[Feature request] TCP/IP support

[unixfox]

Hello,

Could it be possible to add support for TCP/IP, as such that multiple Invidious processes can use one common inv_sig_helper?

Will also ease the setup in containers because TCP/IP communication is much simpler than UNIX sockets as explained here: iv-org/invidious#4789 (comment)

But inv_sig_helper still created just unix domain socket and invidious is automatically using it. So running it in the same container was the easiest and fastest way to get it working for testing since sharing UDS between containers can be tricky and I wasn't going for permanent solution.

Thank you.

[techmetx11]

On Sun, Jul 21, 2024 at 07:11:07AM GMT, Émilien (perso) wrote: Assigned #2 to @techmetx11. -- Reply to this email directly or view it on GitHub: #2 (comment) You are receiving this because you were assigned. Message ID: ***@***.***>

I am working on TCP/IP support at the moment. Thank you

[unixfox]

Very sorry! I didn't mean to create a useless notification. I was assigning you because you assigned yourself on the other issue, so I thought you would want to be assigned here too.

[techmetx11]

It's okay. I should have responded earlier anyway

[unixfox]

Thank you @techmetx11 for the implementation!

I saw that you did set it to 0.0.0.0, but wouldn't it make more sense to set it to listen on 127.0.0.1 by default?

I know in Invidious we would maybe make it listen on 127.0.0.1 by default too: iv-org/invidious#4739

About the implementation, can a user set a custom address and port? In case the port 12999 is already taken or for the host if the user wants to make it listen on another address?

[techmetx11]

On Sun, Jul 21, 2024 at 08:57:31AM GMT, Émilien (perso) wrote: Thank you @techmetx11 for the implementation! I saw that you did set it to `0.0.0.0`, but wouldn't it make more sense to set it to listen on `127.0.0.1` by default?

0.0.0.0 will make it listen on all interfaces, in systems i've tested this on

I know in Invidious we would maybe make it listen on 127.0.0.1 by default too: iv-org/invidious#4739 About the implementation, can a user set a custom address and port? In case the port, 12999 is already taken or for the host if the user wants to make it listen on another address?

Yes, you can do `./inv_sig_helper --tcp 127.0.0.1:8080`

…

-- Reply to this email directly or view it on GitHub: #2 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[unixfox]

On Sun, Jul 21, 2024 at 08:57:31AM GMT, Émilien (perso) wrote: Thank you @techmetx11 for the implementation! I saw that you did set it to 0.0.0.0, but wouldn't it make more sense to set it to listen on 127.0.0.1 by default?
0.0.0.0 will make it listen on all interfaces, in systems i've tested this on

Yes I was telling about the fact if it's a good practice to make this listening on all interfaces by default or not. Because if one runs the program outside of docker then the process may accept requests from the entire internet if the VM is directly exposed on the internet.

[techmetx11]

Hm. Maybe it's not a good idea to listen on 0.0.0.0

…

On Sun, Jul 21, 2024 at 09:04:30AM GMT, Émilien (perso) wrote: > On Sun, Jul 21, 2024 at 08:57:31AM GMT, Émilien (perso) wrote: Thank you @techmetx11 for the implementation! I saw that you did set it to `0.0.0.0`, but wouldn't it make more sense to set it to listen on `127.0.0.1` by default? > 0.0.0.0 will make it listen on all interfaces, in systems i've tested this on Yes I was telling about the fact if it's a good practice to make this listening on all interfaces by default or not. Because if one runs the program outside of docker then the process may accept requests from the entire internet if the VM is directly exposed on the internet. -- Reply to this email directly or view it on GitHub: #2 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>