Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed error from cat when trying nginx.d/* on nodes without vhosts defined #21

Closed
wants to merge 5 commits into from

Conversation

guzmanbraso
Copy link
Contributor

When running first time from scratch, if class was included without any setup at all
and with sane defaults, in debian squeeze generates an error when trying to collect
non existant vhosts, because cat complains that can not expand * because there are no
files.

Added unless to check that at least there is a file in nginx.d by testing it can expand.

Already created an issue for this pull: #20

Thanks!

…vhosts defined

Description:
When running first time from scratch, if class was included without any setup at all
and with sane defaults, in debian squeeze generates an error when trying to collect
non existant vhosts, because cat complains that can not expand * because there are no
files.

Changed:
Added unless to check that at least there is a file in nginx.d by testing it can expand.
…new structure, backwards compatible

Defaults are set inside params, nginx class will set default and send it from local var to nginx::config,
so even when there is no need for set default values on nginx::config, in case someone already using
this module it's for some reason calling directly nginx::config, to avoid breaking anything defaults are
set inside nginx::config too.
Added confd_purge option to tell it to purge files non managed by pupet in conf.d, default is false.
Added confd_purge option to tell it to purge files non managed by pupet in conf.d, default is false.
@guzmanbraso
Copy link
Contributor Author

I'm sorry regarding the extra commits, I'm still learning git :-). Next time will create a branch per issue.

Those commits were going to get into a pull request anyway, so tell me if it's ok or you preffer to remove those from the branch of this pool and submit with another pool request.

@guzmanbraso
Copy link
Contributor Author

Closing this pull, will submit a new one soon.

@guzmanbraso guzmanbraso closed this Oct 1, 2012
fpletz pushed a commit to mayflower/puppetlabs-nginx that referenced this pull request Dec 11, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant