Routing Utilities Testing Deployment Guide Preamble & Disclaimer Deploying Falcon on Linux with NGINX and uWSGI Community Guide Get Help Contribute to Falcon FAQ Changelogs 2.0.0 1.4.1 1.4.0 1.3.0 parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using Nginx’s error_page directive). 500 errors are typically the result of an unhandled exception making its

parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using Nginx’s error_page directive). 500 errors are typically the result of an unhandled exception making its add_static_route(). However, if possible, it is best to serve static files directly from a web server like Nginx, or from a CDN. Misc. How do I manage my database connections? Assuming your database library manages

Deploying Falcon on Linux with NGINX and uWSGI Running your Application as a Different User Preparing your Application for Service Deploying Falcon behind uWSGI Connecting NGINX and uWSGI Further Considerations parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using nginx’s error_page directive). By default, non-system-exiting exceptions that do not inherit from HTTPError

Deploying Falcon on Linux with NGINX and uWSGI Running your Application as a Different User Preparing your Application for Service Deploying Falcon behind uWSGI Connecting NGINX and uWSGI Further Considerations parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using nginx’s error_page directive). By default, non-system-exiting exceptions that do not inherit from HTTPError

Deploying Falcon on Linux with NGINX and uWSGI Running your Application as a Different User Preparing your Application for Service Deploying Falcon behind uWSGI Connecting NGINX and uWSGI Further Considerations parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using nginx’s error_page directive). By default, non-system-exiting exceptions that do not inherit from HTTPError

Deploying Falcon on Linux with NGINX and uWSGI Running your Application as a Different User Preparing your Application for Service Deploying Falcon behind uWSGI Connecting NGINX and uWSGI Further Considerations parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using nginx’s error_page directive). By default, non-system-exiting exceptions that do not inherit from HTTPError

Deploying Falcon on Linux with NGINX and uWSGI Running your Application as a Different User Preparing your Application for Service Deploying Falcon behind uWSGI Connecting NGINX and uWSGI Further Considerations parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using nginx’s error_page directive). By default, non-system-exiting exceptions that do not inherit from HTTPError

Deploying Falcon on Linux with NGINX and uWSGI Running your Application as a Different User Preparing your Application for Service Deploying Falcon behind uWSGI Connecting NGINX and uWSGI Further Considerations parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using nginx’s error_page directive). By default, non-system-exiting exceptions that do not inherit from HTTPError

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.2.2 Deploying Falcon on Linux with NGINX and uWSGI . . . . . . . . . . . . . . . . . . . . . 92 5.3 Community Guide . . . . . . . . . . . parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using nginx’s error_page directive). By default, non-system-exiting exceptions that do not inherit from HTTPError

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.2.2 Deploying Falcon on Linux with NGINX and uWSGI . . . . . . . . . . . . . . . . . . . . . 92 5.3 Community Guide . . . . . . . . . . . parts that have been migrated to Falcon (e.g., by adding an additional location directive to your NGINX config). If the above approach isn’t an option for your deployment, you can implement a simple WSGI Alternatively, you may be able to configure your web server to transform the response for you (e.g., using nginx’s error_page directive). By default, non-system-exiting exceptions that do not inherit from HTTPError