We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As it is becoming really common to install uWSGI on embedded systems, having a "reset to factory defaults" behaviour could be a kick-ass feature.
uwsgi --fallback-config safe_config.ini --ini new_config.ini
if uwsgi fails (exit code 1) the instance is binary patched (as simple execve() ) with
uwsgi safe_config.ini
obviously hosting services can abuse it too ;)
Note: try to place fallback-config directive on top of your config tree to avoid exit(1) being called before its setup
[uwsgi] fallback-config = safe_config.ini socket = 1.2.3.4:3031 master = true psgi = app.psgi
The text was updated successfully, but these errors were encountered:
e8ea1a5
No branches or pull requests
As it is becoming really common to install uWSGI on embedded systems, having a "reset to factory defaults" behaviour could be a kick-ass feature.
uwsgi --fallback-config safe_config.ini --ini new_config.ini
if uwsgi fails (exit code 1) the instance is binary patched (as simple execve() ) with
uwsgi safe_config.ini
obviously hosting services can abuse it too ;)
Note: try to place fallback-config directive on top of your config tree to avoid exit(1) being called before its setup
[uwsgi]
fallback-config = safe_config.ini
socket = 1.2.3.4:3031
master = true
psgi = app.psgi
The text was updated successfully, but these errors were encountered: