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

Add new params to apache::mod::mime class #447

Merged
merged 1 commit into from
Nov 8, 2013

Conversation

ptomulik
Copy link
Contributor

@ptomulik ptomulik commented Nov 8, 2013

This changeset adds $mime_support_package and $mime_types_config parameters to class apache::mod::mime. Their purpose is following:

  • $mime_support_package - install this package, as it provides mime.conf
    file (definition of mime types used by mod_mime),
  • $mime_types_config - used to substitute as TypesConfig in
    mod/mime.conf.erb template.

This PR was created in order to plit #342 into smaller parts to make review process easier, see #342 (comment)

This changeset adds $mime_support_package and $mime_types_config
parameters to class `apache::mod::mime`. Their purpose is following:

- $mime_support_package - install this package, as it provides mime.conf
  file (definition of mime types used by mod_mime),
- $mime_types_config - used to substitute TypesConfig in
  mod/mime.conf.erb template.

This PR was created in order to plit puppetlabs#342 into smaller
parts to make review process easier, see
puppetlabs#342 (comment)
apenney pushed a commit that referenced this pull request Nov 8, 2013
Add new params to apache::mod::mime class
@apenney apenney merged commit 258ad06 into puppetlabs:master Nov 8, 2013
@ptomulik ptomulik deleted the mod_mime_params branch November 8, 2013 18:42
traylenator pushed a commit to traylenator/puppetlabs-apache that referenced this pull request Jun 7, 2022
While the class docker::services already allowed arrays to be
specified for `publish` ports, it didn't handle this correctly since
this array was simply converted to a string and passed onto Docker,
like so:

    --publish '["80:80", "443:443"]'

To correctly publish multiple ports, the `--publish` parameter has to
be called specified for each port.

    --publish '80:80' --publish '443:443'

This patch also introduces a new spec test to check this behavior
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants