Am 15.08.2016 um 12:36 schrieb Adrian Schröter:
no, you can use them on the server, but they are optional. It is just a single script atm for a specific usecase. One that is actually not even recommended.
OK ... which do you use on the server ?
BTW ... ... obs-server should install the rubygem-passendger-apache2 package, which it does not.
It is recommended, but no must to use passenger.
It is used in /etc/apache2/vhosts.d/obs.conf So from my point of view it is required to work ...
... obs.conf (http) should point to an 'existing' dummy cert, which makes apache not to fail on start.
Same here.
It looks like you are looking actually for the appliance which comes with all this. But installing packages manually needs more work on purpose (because you can have various different setups).
Using an appliance is a nice idea, but you'll never understand how this thing works. I want to understand how things work together ... ... and IMHO there should be a 'default' (One possibility of configuration) which should work out of the box. Or do I expect too much ? If I am not happy with the 'default' config, then I can change ... afterwards. Thank you :) P.S.: BTW what happened to apache2 ? a2enmod/a2dismod is without effect ... apache2 loads a 'static' loadmodule.conf which is not updated anymore from APACHE_MODULES of/etc/sysconfig/apache2 ? Why is this wonderful feature gone ? Or is it a BUG ? -- Christian ---------------------------------------------------- - Please do not 'CC' me on list mails. Just reply to the list :) ---------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de ---------------------------------------------------- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org