[chef] Re: Re: Re: Re: chef-solo apache2 install doesn't enable default site

[Yoshi Spendiff < >]

If you want to get mod_php working and enable the default site in apache then you need to make an attributes files and put in some attributes for your cookbook.

Create cookbook/phpapp/attributes/defaults.rb and put in the following:

default['apache']['mpm'] = 'prefork'

default['apache']['default_site_enabled'] = true

You also need to make sure the following is in the metadata.rb of your phpapp cookbook.

depends 'apache2'

Finally, for your knowledge:

The following statements in a recipe are equivalent. Specifying a cookbook without ::<recipe> translates to the default recipe.

include_recipe 'apache2'
include_recipe 'apache2::default'

On Mon, Jun 29, 2015 at 2:10 AM, Joseph Djomeda < " target="_blank"> > wrote:

Hello Guys,

This is getting ridiculous as a simple tutorial is turning into a master level assessment on chef :D . I understood based on @Taylor's explanations and created a virtualhost on my own from the phpapp recipe/templates and soon enough run to this issue : "Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe.  You need to recompile PHP. chef apache2 cookbook" . No fully understanding what this means and with a little google I got to understand that I should rather move away from mod_php . So I downloaded the php-fpm cookbook from the community site and replace php dependency from the metadata file and got this following error put on pastee.org

Nos it's looking for libapache2-mod-fastcgi package. What's the chef way of solving problem like this? Add a repository to the apt/source.d/ to cater for this need as I would have done it manually or there is another way?

Thanks for the help and explanations provided so far.

On Sat, Jun 27, 2015 at 6:38 PM Taylor Price < " target="_blank"> > wrote:

We don't enable the default site by default because it's not good for production use - we attempt to make the cookbook defaults configure apache in a secure way.

On Jun 27, 2015, at 7:31 AM, Joseph Djomeda < " target="_blank"> > wrote:

Hey Taylor,

Looks you are right, never mind, I scrolled down the tutorial and I could do some steps of bringing up a virtualbox and resume from where I am stuck. Setting up of the virtual host on the tutorial is not too far from things I have attempted with web_app, I could not just understood that there should be lots of parameters to cater for just for the default site.

Thanks

On Sat, Jun 27, 2015 at 2:22 PM Joseph Djomeda < " target="_blank"> > wrote:

Hello There,

Below are the modifications I did on my cookbook/phpapp/recipes/default.rb

include_recipe 'apache2'
include_recipe 'apache2::default'

template "#{node['apache']['dir']}/sites-available/default.conf" do
 cookbook 'apache2'
 source 'web_app.conf.erb'
 owner 'root'
 group node['apache']['root_group']
 mode '0644'
# notifies :restart , 'service[apache2]'
end


#web_app "default" do
#       #template 'web_app.conf.erb'
#       #name 'default'
#       server_name 'localhost'
#       enable true
#       docroot '/var/www/html'
#end

apache_site 'default' do
  enable true
end

It produces this output hosted on pastee.org .It looks like it's expecting to see the remaining variable passed to. In that case I would like to ask if there isn't any default variable mechanism in vagrant.

Thanks in advance

On Sat, Jun 27, 2015 at 12:06 PM Joseph Djomeda < " target="_blank"> > wrote:

Hello Guys,

I have been doing a full start from scratch all day chef series in order to start the week with team members and eventually using it through opsworks.

I have an intermediate experience with ansible so I kind of have the big picture with configuration management.

I started with a very modest article from gettingstartedwithchef.com I have already managed to get into trouble. I am running this in vagrant with trusty. I have 2 interfaces Nat and hostonly so I can talk to the vagrant box via it own IP.

My recipe/default.rb really has :
include_recipe 'apache2'

apache_site 'default' do
  enable true
end

What I have noticed is that there is only default-ssl.conf in the sites-available folder and nothing in the sites-enabled folder. As at now I have no idea as to how this happened. I wouldn't want to start rolling out my own virtuahost template because I really want to make sure I follow the steps.

I might switch to another tutorial for the mean time but it will be useful for my own sake to find out what happened and how to debug etc. I will be grateful if anybody and land a hand.

In the meantime any other updated and useful step by step resource on chef is welcome.

Thanks in advance

Best Regards,

--

Yoshi Spendiff

Ops Engineer

Indochino

Mobile: +1 778 952 2025

Email: " target="_blank">