Bootstrap Pristy

This page is reserved for super administrators. Membership in the GROUP_PRISTY_ADMINISTRATORS group alone does not grant access to this page: the Bootstrap Pristy entry only appears in the side menu for a user who holds the native Alfresco administration capability. An unauthorized user who opens the URL directly sees the message “This page is restricted to super administrators.”.

Bootstrap Pristy initializes a Pristy instance: creating accounts and groups, workspaces, folders, uploading e-mail templates, writing configuration files and permissions. Each application serves its own initialization plans, files in YAML format.

The page has two tabs:

  • Common configuration: the list of the instance’s applications,
  • Configuration per application: the wizard that applies an initialization plan.

To change an application’s configuration setting afterwards, the Configuration page is the natural path.

Accessing the page

Click the Bootstrap Pristy entry in the “Administration” section of the side menu.

Common configuration

This tab sets the list of applications offered by the application switcher and by the links in the Pristy Portail side menu. This list applies to the whole instance: it is saved in the common configuration (key APPLICATIONS), read by each application before its own configuration.

A tag shows whether the common configuration already exists (“Common file present”) or not (“No common file”).

The form shows:

  • the Instance base URL: the Fill button rebuilds each application’s address from this URL,
  • one row per application: a switch to offer it or not, its icon (click it to choose another one) and its address. Applications specific to the instance, unknown to the Pristy catalog, are listed after the others and kept as they are.

Three buttons:

  • Initialise (no common configuration) or Reset (existing configuration, after confirmation) fills the form with all the applications of the catalog, built on the base URL,
  • Save writes the list to the repository. The other keys of the common configuration are kept.

Initialise and Reset fill the form without writing: nothing is sent to the server before Save. If no application is enabled, the application switcher will stay empty.

Configuration per application

The wizard runs in four steps: Selection, Variables, Execution Plan and Execution. A plan can be run again safely: each element already present is reported as existing or updated, never duplicated.

Step 1 - Selection

Choose the Instance that serves the plan by clicking its tile: Portail, Espaces, Marches, Social, Media, Actes, or Other… to enter a custom, complete Base URL (for example https://example.com/espaces/).

For an instance from the list (other than Portail), the base URL is determined from the address configured for that application; for Portail, the origin of the current page is used.

The plans offered by the application are then displayed under Init file, one tile per plan with its title, description and file name. This list is read from the application’s manifest (init-manifest.yaml). Without a manifest, a warning is displayed and the default list is offered, whose files may not exist:

FileTitleContent
init.yamlInitialisationGroups, service accounts, folders and configuration files required by the application
init-demo.yamlDemonstrationDemonstration accounts, workspaces and memberships, whose names can be changed
init-emails.yamlE-mail templatesFreeMarker templates for notification, invitation and password reset
init-env-config.yamlPortal configurationThe application’s env-config.json file

init.yaml creates no demonstration account or workspace: it can be applied to a production instance. init-demo.yaml is applied after init.yaml, whose groups it uses.

The Load button downloads the chosen plan and parses it. A loading or YAML parsing error is displayed under the fields, without leaving this step.

Step 2 - Variables

The plan can contain variables, in the form {{ nom_variable }} or {{ nom_variable | default(valeur) }}. The wizard offers a field for each one, with a label provided by the plan and the variable name:

  • a default value of true or false displays a switch. A switch can include or exclude optional elements of the plan (a demonstration classification plan, for example): the fields used only by the excluded elements are hidden,
  • a random password is generated on load and displayed in clear text, with a Regenerate button: it will be the password of the created account,
  • any other variable displays a text field, pre-filled with its default value.

The variables used by the external files referenced by the plan (source property) are also offered. An external file that cannot be found or read is ignored with no message on screen.

If the plan contains no variable, this step is skipped. The Analyze button starts the comparison with the repository.

Step 3 - Execution Plan

The wizard compares each element of the plan with the repository, then displays it, phase by phase: Users, Groups, Memberships, Sites, Site Members, Configurations, Folders, Files, Permissions. Three counters summarize the plan: elements to create, existing and to update.

Each row carries a status:

  • Create: the element does not exist,
  • Existing: the element exists and requires nothing,
  • Update: the element exists and will be rewritten,
  • Error: the comparison failed, the details are displayed under the status.

Users, groups, memberships, sites, site members and folders are compared on their existence alone. Files and configurations are compared on their content: identical content is marked Existing, and a plan applied again to an up-to-date instance rewrites nothing.

  • A file is compared by its SHA-256 fingerprint, computed by Pristy Core. If the fingerprint of the stored file is not available, the file is marked Update, with a “No fingerprint available” icon. This is always the case when Pristy Core does not offer the hash.content capability (version earlier than 4.9, or fingerprints disabled).
  • A configuration is compared as JSON, regardless of key order.

For a file or a configuration that differs, the Diff button opens a side-by-side comparison: “Stored content” on the left, “Plan content” on the right. Binary files have no comparison.

Clicking the Create or Update tag of a row applies that element alone, without going through step 4.

Before clicking Apply, check each row, especially the elements marked Update, which overwrite existing content. The Permissions of a folder are always marked Update.

The Back button resets the wizard to step 1. The Apply button is disabled if the plan contains no element to create or update; otherwise, it runs the whole plan.

Step 4 - Execution

The wizard applies each element of the plan in the order of the table, except the Existing elements. Elements marked Error at step 3 are retried. An indicator shows the current row; the details of an error are displayed under the status of the row concerned.

At the end, a message summarizes the number of elements created and updated, and the number of errors, if any.

Created accounts

Each account created by the execution (whole plan or single row) is listed in the Created accounts panel, with its identifier and password. The Copy credentials button copies them to the clipboard, one account per line. An account that already exists keeps its password and is not listed.

Write these passwords down immediately: they are stored nowhere and are no longer displayed after leaving the page.

The Back button resets the wizard to step 1, which lets you continue, for example, with init-demo.yaml after init.yaml.

Common use cases

First installation

After deploying a Pristy server:

  1. in the Common configuration tab, initialize then save the list of applications,
  2. apply init.yaml of each deployed application (Portail, Espaces, then the others as needed),
  3. for a demonstration instance, then apply init-demo.yaml.

Updating e-mail templates

Apply init-emails.yaml from the Portail instance.

The Pristy - Configuration folder of the Data Dictionary and the PRISTY_ADMINISTRATORS group are created at Alfresco startup by Pristy Core: they require no manual action.


Last Update - November 5, 2026
Call To Action 📣

Try Pristy

You can try the Pristy demo by signing up using the link below.

Demander une démo