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.
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
Allow reflex run to support non interactive mode #2859
Comments
Hey @PasqualePuzio Thanks for bringing this up. We recently merged in this PR #2867 that looks for the next available slot. Check this out and let me know your thoughts |
Hi @ElijahAhianyo thank you for pointing that out. Please let me know if i've been clear enough or not. |
@PasqualePuzio the PR linked above #2867 removes those interactive options (there will be no more kill/change options in the next release) and just starts your app on a new available port, so there should be no more interactive mode in The When you say deploy, you mean to a hosting provider? In that case how are there multiple apps running together? |
Sure, I agree with you. However I was raising the issue because in a production environment you really dont' want to change the port because that means you have to change the configuration of the load balancer or reverse proxy as well (nginx for instance). |
Got it - we could have a flag in |
yes, that would be great. It would be even better if that could be done with zero downtime, so that both the frontend and the backend never stop responding. |
Not sure if we can accomplish the zero downtime requirement easily, will have to think more on that. But yes we can add a flag that makes sure it uses the default port rather than auto changing. |
Right now, if reflex is already running and you execute
reflex run
(either in prod mode or not), the tool shows a prompt and lets you decide whether you want to kill the current process, change it or exit.First of all, I think it would be useful for production use-cases (where you want to achieve zero downtime) to add a command line argument in order to disable interactive mode and force the system to kill (or change) any previously running processes.
Also, I was wondering what's exactly the difference between kill and change? How do they affect the running processes? Do you have any recommendations to avoid downtime when running a new version of the app?
Thanks
The text was updated successfully, but these errors were encountered: