[jira] [Commented] (AIRFLOW-82) Add configuration option in airflow.cfg for Flask APPLICATION_ROOT

["Ivan Levchenko (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903978#comment-15903978 ] 

Ivan Levchenko commented on AIRFLOW-82:
---------------------------------------

This would be a big deal for me. Currently doing html rewriting in apache to get to this to work. 

> Add configuration option in airflow.cfg for Flask APPLICATION_ROOT
> ------------------------------------------------------------------
>
>                 Key: AIRFLOW-82
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-82
>             Project: Apache Airflow
>          Issue Type: Wish
>            Reporter: Sean McIntyre
>            Priority: Minor
>              Labels: feature, suggestions
>
> For various reasons, I might not have the flexibility to use a domain or subdomain root, e.g., airflow.myorg.com) as the entry point to Airflow. Instead I may have to use something like myorg.com/airflow/.
> Fortunately Flask has the APPLICATION_ROOT configuration option which makes this easy if URLs are rendered with the Flask url_for method.
> I believe this feature is added in two steps:
> 1. Add configuration option logic to flow from airflow.cfg to instantiation of Flask.
> 2. Go through existing template files and convert to using Flask url_for methods.
> 3. (hidden step) Encourage other contributors to use url_for going forward.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)