Pristy Configuration Initialization

Each Pristy application (Portail, Espaces, Actes, Marchés, Social, Média) is configured by an env-config.json file stored in a subfolder named after it in the Pristy - Configuration folder of the Alfresco Data Dictionary. The settings shared by all applications, such as the list of the instance’s applications, are stored in a common configuration, the common subfolder.

Initializing an instance

Initialization is done from Pristy Portail, with a super administrator account: Administration menu > Bootstrap Pristy. The page applies the initialization plans that each application declares in its init-manifest.yaml manifest (by default init.yaml, init-demo.yaml, init-emails.yaml, init-env-config.yaml) and sets the common configuration.

How it works is described in Bootstrap Pristy.

Changing the configuration

To change a setting of an installed application, use the Configuration page, available in Pristy Portail, Espaces, Marchés and Média. Pristy Social offers raw JSON editing.

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, media), or with common for the common configuration. The account must be an Alfresco administrator or a member of GROUP_PRISTY_ADMINISTRATORS.

The curl method sends the file as-is without merging with the existing configuration. Make sure the file contains all required parameters. The static parameters it contains (ALFRESCO_HOST, AUTH…) are removed when saving. The previous version remains available in the file’s version history.


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