[
https://issues.apache.org/jira/browse/AURORA-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639835#comment-14639835
]
Kevin Sweeney commented on AURORA-1408:
---------------------------------------
I'm not convinced we even need to explicitly add support for this - it's
possible today with the Thrift API and the CORS flags (and the generated Thrift
JS client is even served from /apiclient if new UIs find that toolchain too
heavyweight).
So +0 - this is nice to have but not a requirement for someone who wants to
build a new UI (or even iterate on one in parallel).
> Add the ability for the scheduler to serve the UI from an arbitrary path
> ------------------------------------------------------------------------
>
> Key: AURORA-1408
> URL: https://issues.apache.org/jira/browse/AURORA-1408
> Project: Aurora
> Issue Type: Task
> Components: Scheduler, UI
> Reporter: Joshua Cohen
> Priority: Minor
>
> There's been discussion about giving Aurora operators the ability to swap out
> the UI with one of their choosing. This would be useful for deploying a
> custom UI or just for testing purposes.
> The majority of the groundwork for this ability has already been laid, but
> there are likely some tweaks that still need to be made with regard to the
> jersey/jetty configuration as well as the obvious need to add a command line
> flag that specifies the path from which the UI should be served.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
