search

sous-chefs / apache2

Development repository for the apache2 cookbook
https://supermarket.chef.io/cookbooks/apache2
Apache License 2.0
284 stars 548 forks source link

SuSE default 'apache/dir' attribute issue #179

Closed rednevals closed 10 years ago

rednevals commented 10 years ago

I had success setting up a prototype Gerrit site on CentOS using the Gerrit cookbook(https://github.com/TYPO3-cookbooks/gerrit), which references apache2. Now I am in attempting to setup the production site on a SuSE VM.

The first issue that I ran up against with the apache2 cookbook is the default attributes, specifically the apache/dir. The apache2 default recipe is attempting to create sites-available, sites-enabled, mods-available, and mods-enabled and fails, because the target directory('/etc/httpd') does not exist.

The default attributes for 'suse' are lumped together with 'redhat', 'centos', etc. During my chef-client run, apache2 package is installed, not httpd. So, the value for apache/dir is incorrect.

Is this something that needs to be addressed in the default attributes, maybe by creating a separate 'suse' case? Or, do I just need to override this particular attribute?

Then I wonder how many of the other defaults will be incorrect as well. Maybe we need to just move 'suse' to the 'debian' case.

drpebcak commented 10 years ago

This is definitely something that can be changed in the attributes. We don't test on suse at all, so I'm not surprised if there are differences.

Likely there are several attributes for suse that are inaccurate.

If you want to go ahead and work through updating the attributes section, please feel free! You'll likely want to work against the COOK-3900 branch for now.

svanzoest commented 10 years ago

Hi!

Thank you for using the apache2 cookbook. We currently actively working on the COOK-3900 branch on adding Apache 2.4 support to the cookbook. Currently SuSE not something we have been testing SuSE. We would love to add better support for this platform and I specificly created a milestone for this and added some of the older tickets from before we took over the cookbook.

I think the best way to approach SuSE support is by adding it to the .kitchen.yml and work on making the chefspec and serverspec tests pass on that platform.

We usually hang out at https://gitter.im/onehealth-cookbooks/apache2 in case you would like to discuss adding SuSE support in more real-time.

rednevals commented 10 years ago

The issue that I have with proceeding with a separate 'suse' case is that I don't know enough about apache2 to know how many other attributes need to be defined and what their values are. I'll forge ahead and see how it goes.

I wonder if anyone as tried this on SuSE ;)

svanzoest commented 10 years ago

@rednevals I have grouped all the SuSE related tickets I could find https://github.com/onehealth-cookbooks/apache2/issues?milestone=4 and we will support you any way we can.

rednevals commented 10 years ago

Sorry, being locked into the Equifax VPN, I am not able to get to the IM site.

I am a beginner++ at chef, so please be gentle.

rednevals commented 10 years ago

I submitted one more change today that is getting me closer. I made sure to merge the latest upstream changes first, before creating the pull request. I might try to get on the IRC on my MacBook later...

Any recommendations on an OS X IRC client, or is that not needed?

drpebcak commented 10 years ago

@rednevals the gitter chat is not an IRC channel - you access it via a web browser.

Although if you are looking for an IRC client, my personal favorite is limechat. :)

svanzoest commented 10 years ago

This was addressed in debfdc80 as part of #180

lock[bot] commented 6 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.