Freek de Kruijf wrote:

With the appearance of apache2 version 2.4 in openSUSE 13.1 and Factory. the module yast2-http-server is no longer usable.

I studied the ruby code, but I don't think I will be able to adopt it to the requirements of apache2 2.4, without putting a lot of effort in it, but it will take too long time to complete.

I have a general idea about what needs to be changed, so when there is somebody who is knowledgeable in ruby and in the details of how a yast2 module must be made, I can give directions on what the module needs to do.

I'll be glad to help too, but I do not have the time to dedicate to active work in/on yast2.

This all is under the condition that the community has a need for such a module.

Personally I don't, but YaST's ability to help get the newbie started has sofar been a significant strength for openSUSE. I would hate to lose it. -- Per Jessen, Zürich (4.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, 14 Nov 2013 21:42:29 +0100 Freek de Kruijf <f.de.kruijf@gmail.com> wrote:

With the appearance of apache2 version 2.4 in openSUSE 13.1 and Factory. the module yast2-http-server is no longer usable.

I studied the ruby code, but I don't think I will be able to adopt it to the requirements of apache2 2.4, without putting a lot of effort in it, but it will take too long time to complete.

I have a general idea about what needs to be changed, so when there is somebody who is knowledgeable in ruby and in the details of how a yast2 module must be made, I can give directions on what the module needs to do.

This all is under the condition that the community has a need for such a module.

Hi Freek, at first I must say, that for me yast2-http-server have really bad design and target group. The biggest problem is that want to edit(!) apache configuration. It means that such module must keep user specific options and change ones, that are important for given ability. Apache configuration is almost script, so recognize what it do is quite hard, as it allows various conditions regexp expansions and so on. For me http-server is almost dead project ( but yast team, still do not mark it as dropped ). If we want revive it, then it must be completely changed and have different use case. For me perfect use case for newbies is to have such module as start-up project to quickly run server of needs and use cases can be - give me server with static files from given dir - give me server with php from given dir - give me server with rails from given dir - give me server with django from given dir and so on and only guarantie, is that it configure apache ( breaks things! ) to run web server. Otherwise it is almost unmaintainable. Just my 2c and it is not officical suse or yast team statement. Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 11/14/2013 09:42 PM, Freek de Kruijf wrote:

With the appearance of apache2 version 2.4 in openSUSE 13.1 and Factory. the module yast2-http-server is no longer usable.

I studied the ruby code, but I don't think I will be able to adopt it to the requirements of apache2 2.4, without putting a lot of effort in it, but it will take too long time to complete.

I have a general idea about what needs to be changed, so when there is somebody who is knowledgeable in ruby and in the details of how a yast2 module must be made, I can give directions on what the module needs to do.

This all is under the condition that the community has a need for such a module.

Hi, Do you have any more details on what's wrong and what needs to be changed? Of course, Josef's idea of simple workflows would make more sense than the current HTTP Server approach. As he alread pointed out, it's nearly impossible to implement Yast code that parses and `understands` the whole apache config file. Only apache itself can do it but then apache can't write the cnfig file. Anyway, now we can focus on fixing the biggist issues but we have to know the details. Thanks in advance Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org