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.

Sign up for GitHub

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

Jump to bottom

On-the-fly config file reload #46

Open
Feliksas opened this issue Jun 1, 2018 · 4 comments · May be fixed by #316
Open

On-the-fly config file reload #46

Feliksas opened this issue Jun 1, 2018 · 4 comments · May be fixed by #316

Comments

@Feliksas
Copy link

Feliksas commented Jun 1, 2018 •
edited
Loading

Would be very nice to add a feature to reload the config without restarting the proxy, for example, by SIGHUP and/or automatically (inotify)
@seega
Copy link

seega commented Jun 1, 2018

docker stop mtproto-proxy && docker rm mtproto-proxy && docker run -d [etc]
takes 7 seconds for me, is it critical?

@stek29
Copy link
Collaborator

stek29 commented Jun 1, 2018

@seega it takes 7 seconds and drops all connections (it's not that important in context of mtproto-proxy, but still undesired)

@seriyps
Copy link

seriyps commented Jun 10, 2018

You may try my mtproto proxy server, it supports promoted channels and it updates configs periodically in background without restarts https://github.com/seriyps/mtproto_proxy

@stek29 stek29 mentioned this issue Jun 26, 2018
Closed
@dvershinin
Copy link

+1 for SIGHUP signal handling implementation. Like normal Linux services would do.

@dvershinin dvershinin linked a pull request Jun 28, 2019 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

SIGHUP handler for reloading config dvershinin/MTProxy
5 participants
@dvershinin @seriyps @Feliksas @stek29 @seega