Pristy Configuration Initialization

Each Pristy application (Portail, Espaces, Actes, Marchés, Social) is configured by an env-config.json file stored in the Pristy - Configuration folder of the Alfresco Data Dictionary.

Configuration initialization is done from the Pristy Portail administration interface.

Prerequisites

The Pristy - Configuration folder and base groups (PRISTY_ADMINISTRATORS) are automatically created at Alfresco startup by the pristy-core module. No manual action is required for this step.

Accessing initialization

1. Log in to the Pristy Portail with an Alfresco Administrator account
2. Open the Administration menu
3. Click on Bootstrap Pristy

Initialization wizard

The wizard guides the administrator through four steps.

Step 1: Selection

Choose the application to initialize and the initialization type:

For each application, three initialization files are available:

Step 2: Variables

If the initialization file contains variables (passwords, domain names…), the wizard displays a form to fill them in.

Passwords are pre-filled with a secure random value. Other variables display their default value which you can modify.

This step is skipped if the file contains no variables.

Step 3: Plan (preview)

The wizard analyzes the file and displays a summary of planned actions:

• Create: elements that do not yet exist on the server
• Existing: elements already present (skipped)
• Update: elements to modify

Details are displayed by phase (users, groups, members, sites, folders, files, permissions).

Step 4: Execution

Click Execute to apply the actions. Progress is displayed in real time. At the end, a summary shows the number of elements created, updated, or skipped.

Common use cases

First installation

After deploying a Pristy server, run the complete initialization for each deployed application:

1. Portail → init.yaml
2. Espaces → init.yaml
3. Other applications as needed

This creates groups, configuration folders, env-config.json files, and permissions.

Configuration update

To modify an application’s configuration (for example, enable a module or change a parameter):

1. Portail → init-env-config.yaml
2. Review the plan (the existing env-config appears as “Update”)
3. Execute

Email templates update

To deploy or update Alfresco email templates (notifications, invitations, password reset):

1. Portail → init-emails.yaml
2. Execute

Manual method (curl)

For a one-off update of a single configuration file, you can use curl directly:

ALF_ADMIN=admin
ALF_PASS=
curl -X PUT https://server.pristy.net/alfresco/s/fr/jeci/pristy/config/espaces/env-config.json \
  --user "${ALF_ADMIN}:${ALF_PASS}" \
  -H 'Content-Type: application/json' \
  --data "@/path/to/env-config.json"

Replace espaces in the URL with the target application name (portail, actes, marches, social).