-
-
Save Spredzy/0cfe034c921410a52e9d to your computer and use it in GitHub Desktop.
profile model
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
What would you recommend ? | |
class profile::lamp { | |
include ::apache | |
include ::apache::mod::php | |
include ::mysql::server | |
include ::mysql::bindings | |
include ::php | |
} | |
class profile::wordpress { | |
include profile::lamp | |
include ::wordpress | |
} | |
or | |
class profile::wordpress { | |
include ::apache | |
include ::apache::mod::php | |
include ::mysql::server | |
include ::mysql::bindings | |
include ::php | |
include ::wordpress | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Both are functionally the same underneath the hood. The benefit of the first example is that profile::lamp stands alone and you don't need to update profile::wordpress with changes that profile::lamp may need.
I will usually implement the former bit. What's funny is that I have a post started on just this very question - so look out for it in the near future :)