Local ProfilesIntroduced in Tiki12.
Local profiles can be used to store configurations locally without the need for an external profile repository, running as a Tiki instance.
The local profile repository is a simple directory available on the local filesystem. Profiles are a single file with the .yml extension. A directory with the same name (without the file extension) is used to pull any page that may be referenced within the profile.
Unlike profiles stored in the normal repositories, local profiles are not wiki syntax with CODE blocks containing the actual YAML definitions. This structure allows for text editors to properly hightlight the syntax.
--- preferences: feature_wiki: y objects: - type: wiki_page ref: about_profile data: name: About Profile content: wikicontent:PageContent # ^ Referenced page in sub-directory
Any content. References are handled like normal profiles.
You would then apply this profile with a command like:
php console.php profile:apply Sample file://my_repository
By default, when you export a profile through the command line, it gets exported into a brand new folder called "profiles" in the tiki root folder. Therefore, you can clone that folder structure to a new server, inside the equivalent tiki root, and apply your profile with the command:
php console.php profile:apply Sample file://profiles
How to make a local profile out of an existing tiki siteYou can use the commands provided with console.php.
See: Export Profiles
About PatchesWhen used as database patches, local profiles use installer/schema/ as the repository directory, and the patch names are used as the profile names. Patches are applied in sequence based on their file name.
Alias names for this page: