Profile dependencies can be used to build a large profile out of smaller "mini" or "sub" profiles. For example, if you want to have a more modular version of the
Company Intranet profile you can use dependencies to include the blog configuration, and then use that same blog configuration in another profile.
Dependencies Syntax
MyConfigurationRepositoryProfile
{CODE(caption=>YAML)}
dependencies: # Could also be called dummy
- $profiles.tikiwiki.org:BugTrackerProfile:bug_tracker
- $profiles.tikiwiki.org:ClientManagementProfile:client_tracker
- $profiles.tikiwiki.org:SampleDataProfile:sample_page
{CODE}
Current Limitations
- Dependencies need to be all in one YAML block.
- The referenced profiles need to be named without spaces or join words using underscore only (no spaces or dashes, ex: User_Tracker)
- If the referenced profiles contain profile requests (for user input), they do not appear when installed as dependency profile within another "parent" profile.
By installing the
MyConfigurationRepositoryProfile profile, the following profiles would be installed:
- MyConfigurationRepositoryProfile (everything on the original page.)
- BugTrackerProfile
- ClientManagementProfile
- CategoryTreeProfile (if this profile is referenced in ClientManagementProfile for example)
- SampleDataProfile