Skip to content
This repository was archived by the owner on Feb 29, 2024. It is now read-only.

Conversation

@jamielennox
Copy link
Contributor

Zuul V3 has tenant names in the URLs so they are much more variable.
This means that we can't simply rely on hardcoding a couple of paths
into our apache config and we should probably just forward everything to
the zuul app.

Signed-off-by: Jamie Lennox jamielennox@gmail.com

Zuul V3 has tenant names in the URLs so they are much more variable.
This means that we can't simply rely on hardcoding a couple of paths
into our apache config and we should probably just forward everything to
the zuul app.

Signed-off-by: Jamie Lennox <jamielennox@gmail.com>
@ConsoleCatzirl
Copy link
Contributor

Doesn't this mean that we will no longer be serving /opt/source/zuul/etc/status/public_html/ and so no longer serving the website displaying the states of the pipeline queues? If so, should we create a new vhost to serve that public_html directory so that we can still have a website showing the states of the pipeline queues?

@omgjlk
Copy link
Contributor

omgjlk commented May 4, 2017

I think the web app itself takes care of the pipeline states.

@jamielennox
Copy link
Contributor Author

I... don't know. The webapp is broken on v3 so i haven't been able to check.

Is there a way we can prioritize serving the static files?

@ConsoleCatzirl
Copy link
Contributor

It looks like rewrite rules allow for PCRE, so we can glob the tenant portion similar to how we glob the current status rewrite.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants