On Mon, Sep 26, 2011 at 23:53, Joop Boonen <joop.boonen@boonen.org> wrote:
I found another way to "fix it" and not "jeopardize" security.
--- /srv/www/obs/webui/config/environments/production.rb.orig 2011-09-21 12:57:27.000000000 +0200 +++ /srv/www/obs/webui/config/environments/production.rb 2011-09-22 21:16:57.620321787 +0200 @@ -15,8 +15,8 @@
# Host name gets changed by obsapisetup on each boot FRONTEND_HOST = "localhost" -FRONTEND_PORT = 81 -FRONTEND_PROTOCOL = 'http' +FRONTEND_PORT = 444 +FRONTEND_PROTOCOL = 'https'
If this is an option can this be put in git or in /usr/share/doc/packages/obs-api/README.SETUP
As far as I can tell, only the README.SETUP changes from above have been included and are distributed with obs-{server,api} in version 2.2.994-1.3, correct? (The apache2/vhost/obs.conf change is not included.) The setup docs as they are now do NOT result in a working OBS: When apache and obsapidelayd are started and it's time to run curl or browse the webui (step 4.1), the latter only displays the very unhelpful message "Unable to connect to API host. (localhost)". curl displays a similar error. Being a newbie, I am unable to debug this problem with the docs. I cannot comment on the security of the 444/https fix, but at least it works; I haven't tested the obs.conf fix. Please update the docs, and test them, because right now they are broken. (I have found some more small errors in the docs, I'll push those via git directly because they're mostly trivial.) -- Kind regards 686f6c6d / Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org