[GH-ISSUE #111] Possibility to have multi user configuration #94

New issue

Open

opened 2026-02-25 20:32:24 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 20:32:24 +03:00

Owner

Originally created by @kidburglar on GitHub (Apr 9, 2017).
Original GitHub issue: https://github.com/asapach/peerflix-server/issues/111

Hello,

I was thinking, maybe it would be possible to split the inferface from the application.
So we can host the interace with a webserver and connect to different socket from the interface like ruTorrent do for rTorrent.

It would avoid multiple webservers for each users and I think it will simplify the configuration for multiple users too.

Cheers.

Originally created by @kidburglar on GitHub (Apr 9, 2017). Original GitHub issue: https://github.com/asapach/peerflix-server/issues/111 Hello, I was thinking, maybe it would be possible to split the inferface from the application. So we can host the interace with a webserver and connect to different socket from the interface like ruTorrent do for rTorrent. It would avoid multiple webservers for each users and I think it will simplify the configuration for multiple users too. Cheers.

kerem added the

enhancement

label

2026-02-25 20:32:24 +03:00

kerem commented

2026-02-25 20:32:25 +03:00

Author

Owner

@asapach commented on GitHub (Apr 10, 2017):

So you would have one frontend and multiple backends? How do you choose which backend to connect to? How do you envision the user experience?
I like the idea, but there are some technical challenges, e.g. currently frontend code is pretty much tightly coupled to the backend logic and decoupling them means formalizing the protocol and maintaining some kind of versioning / backwards compatibility.

@asapach commented on GitHub (Apr 10, 2017): So you would have one frontend and multiple backends? How do you choose which backend to connect to? How do you envision the user experience? I like the idea, but there are some technical challenges, e.g. currently frontend code is pretty much tightly coupled to the backend logic and decoupling them means formalizing the protocol and maintaining some kind of versioning / backwards compatibility.

kerem commented

2026-02-25 20:32:25 +03:00

Author

Owner

@kidburglar commented on GitHub (Apr 10, 2017):

That is a good question, I never did nodejs so I can only compare to rutorrent / rtorrent.

rtorrent listen to diferent port / socket that depend of the user configuration file (~/.rtorrent.rc)

ruTorrent display the interface and connect on the port / socket that is given in his configuration file and in apache / nginx.
ruTorrent match the configuration with the login that we use when we login with apache authorization.

I don't know if I'm really clear, if you need configuration files or more information don't hésitate to ask.
Cheers.

@kidburglar commented on GitHub (Apr 10, 2017): That is a good question, I never did nodejs so I can only compare to rutorrent / rtorrent. rtorrent listen to diferent port / socket that depend of the user configuration file (~/.rtorrent.rc) ruTorrent display the interface and connect on the port / socket that is given in his configuration file and in apache / nginx. ruTorrent match the configuration with the login that we use when we login with apache authorization. I don't know if I'm really clear, if you need configuration files or more information don't hésitate to ask. Cheers.

kerem referenced this issue

2026-03-15 02:53:58 +03:00

[GH-ISSUE #94] npm coughs and rolls over. #295