[chef] Re: opscode nginx_site disable not working as expected

[Mike < >]

To disable the pre-installed default site, you probably need to do:

nginx_site '000-default' do
  action :disable
end

instead.

This is probably a bug in the cookbook (I admit, I wrote the disable
part a long time ago, and at the time it worked for me), since there's
supposed to be an attribute you can use to control this behavior. Ref:
https://github.com/opscode-cookbooks/nginx/blob/master/attributes/default.rb#L80

If that doesn't work, feel free to report a bug, and send it my way.

Some packages may auto-enable the default site, and since nginx reads
site definitions alphabetically, it is common for the file to be named
000-default to be the first one loaded.

-M

On Thu, Apr 4, 2013 at 4:49 AM, Sachin Sagar Rai 
<
 >
 wrote:
>
> Hi,
> I installed the nginx using the opscode cookbook nginx
> https://github.com/opscode-cookbooks/nginx
>
> And this is the last code of my recipe:
>
> …
> nginx_site 'default' do
>   action :disable
> end
>
> nginx_site app_name do
>   action :enable
> end
>
> After going into /etc/ngins/sites-enabled, I see:
>
> lrwxrwxrwx 1 root root   34 Apr  4 08:38 000-default ->
> /etc/nginx/sites-available/default
> lrwxrwxrwx 1 root root   37 Apr  4 08:32 harstorage ->
> /etc/nginx/sites-available/harapp
>
> The question is, why just instead of removing the symlink, it renamed from
> `default` to `00-default`?
> It should have removed the link, why this?
>
> -------------------------------------------
> @millisami
> ~ Sachin Sagar Rai
> Ruby on Rails Developer
> http://tfm.com.np
> http://nepalonrails.com
> http://funsole.com
> Sent with Sparrow
>