Scout24/yum-repo-server

Make yum-repo-server work in a non-root context

visibilityspots opened this issue · 4 comments

visibilityspots commented

When deploying the yum-repo-server using the naming "yum-repo-server" in the webapps directory of jetty the whole thing is pretty broken because of some hard coded links to root.

If I rename the yum-repo-server application container to ROOT/ everything is working fine.

Is this an issue or is there a specific reason for this behaviour?

Thanks in advance

oli99sc commented

Hi Jan, well the main reason is, that we deploy it into the root context. Which is a bad reason.
Need to check how much the repoclient also relies on this, I am not very familiar with its config options.
If this is a problem for you, it is an issue.
Best, Oli

Von meinem iPhone gesendet

Am 15.05.2014 um 13:27 schrieb Jan Collijs notifications@github.com:

When deploying the yum-repo-server using the naming "yum-repo-server" in the webapps directory of jetty the whole thing is pretty broken because of some hard coded links to root.

If I rename the yum-repo-server application container to ROOT/ everything is working fine.

Is this an issue or is there a specific reason for this behaviour?

Thanks in advance

—
Reply to this email directly or view it on GitHub.

mriehl commented

You are right @oli99sc , the repoclient assumes a root context. It's easy enough to fix, but an issue there too nevertheless.

mriehl commented

repoclient can now deal with a non-root context. I'm renaming this issue to make it clear what needs to be done.

oli99sc commented

Everything I tested manually now works for me in yum-repo-server context.
Still need to work out a setup for some automatic tests, that ensure this during regression.
Simply symlinking in webapps dir to start app twice does not work, as some JMX beans than conflict in the VM. May need to add web context name to MBeans or have a differently configured server.