Abhishek1559 commented on issue #54402: URL: https://github.com/apache/airflow/issues/54402#issuecomment-3218932346
Hi All, I did the analysis and had few observations. In development (using Breeze), we can access the base_url value if we export AIRFLOW__API__BASE_URL="your-path" inside the Breeze terminal (or by adding it to [init.sh], etc). That works fine for the development, not for production. A way around this can be, explicitly setting up the base_url (equals to a hard coded/default value), however that is not recommended. Similar trends for configs are observed for other variables in issues like #53972. Also, specific to this config issue, ‘’’ base_url has been moved to [api] from webserver. It is used by the API server for building external links (task log URLs, trigger endpoints, etc.). The webserver (UI) no longer respects base_url; it expects you to put Airflow behind a reverse proxy (e.g., NGINX) and handle subpath rewrites there. ‘’’ The solution for this is to follow the following document while running in production. https://airflow.apache.org/docs/apache-airflow/2.6.2/howto/run-behind-proxy.html OR Simply manually setting up the base_url in airflow.cfg to the desired path. If I have misunderstood or missed anything, feel free to point out and guide. Also, @potiuk similar config issue trends are been observed after 3.x.x versions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
