Installing Pristy on Alfresco

Preparation

Prerequisites: Alfresco Community 25.3 on Tomcat, with Java 17, Solr and Transform Core AIO.

Installing the pristy-core-platform module

  • Stop the service
systemctl stop alfresco
shell
  • Add the module to your modules installation folder $TOMCAT_HOME/amps
$TOMCAT_HOME/amps
mv $DOWNLOAD_DIRECTORY/pristy-core-platform-xxx.amp $TOMCAT_HOME/amps/
shell
  • Deploy the modules from the amps folder
amps
java -jar $TOMCAT_HOME/alfresco-mmt/alfresco-mmt-*.jar \
install $TOMCAT_HOME/amps/ $TOMCAT_HOME/webapps/alfresco \
-nobackup -directory -force
shell
  • Restart alfresco to apply the module installation

Change the value of reset-password.secret_key in alfresco-global.properties: it is secretKey by default.

Optional modules

The other modules are installed the same way, in the amps folder:

  • pristy-actes, pristy-marches, pristy-social: content models of Pristy Actes, Pristy Marchés and Pristy Social,
  • pristy-collab: real-time collaborative editing of text files,
  • pristy-kafka-platform: Kafka event bus,
  • collabora-platform-extension: online editing with Collabora Online,
  • send-mail-platform: sending documents by email.

The Kafka and Collabora modules need their own properties in alfresco-global.properties: see the README of their repository.

Setting up Pristy interfaces

If your server does not have a reverse proxy in front of Alfresco, you can install the applications directly as webapps in Tomcat.

The applications are built for the /portail/ and /espaces/ paths: the folders must have these names.

pristy-portail

tomcat
mkdir -p $TOMCAT_HOME/webapps/portail
cd $TOMCAT_HOME/webapps/portail
tar xzf $DOWNLOAD_DIRECTORY/pristy-portail-xxx.tgz package/dist --strip-components=2
chown -R alfresco:alfresco $TOMCAT_HOME/webapps/portail
shell

pristy-espaces

tomcat
mkdir -p $TOMCAT_HOME/webapps/espaces
cd $TOMCAT_HOME/webapps/espaces
tar xzf $DOWNLOAD_DIRECTORY/pristy-pristy-espaces-xxx.tgz package/dist --strip-components=2
chown -R alfresco:alfresco $TOMCAT_HOME/webapps/espaces
shell

User for chown on pristy-portail and pristy-espaces
Make sure to correctly specify the user that starts the tomcat process.

Configuration

The env-config.json file of each application only holds the static parameters. Replace $TOMCAT_HOME/webapps/portail/env-config.json and $TOMCAT_HOME/webapps/espaces/env-config.json with:

env-config.json
{
  "ALFRESCO_HOST": "https://pristy.example.org",
  "ALFRESCO_AUTH": "BASIC",
  "ALFRESCO_ROOT": "alfresco",
  "AUTH": "basic"
}
json

ALFRESCO_HOST is the address used to reach tomcat. The applications read the rest of their configuration from Alfresco, under /alfresco/ on the same server.

This configuration is created by the Bootstrap: log in to Pristy Portail with a super administrator account and run Bootstrap Pristy, as described in Configuration Initialization. The displayed metadata are then set from the Metadata page of Pristy Espaces.

Testing

You can access the following applications:

  • pristy-portail : http[s]://serveur_tomcat:port_tomcat/portail/
  • pristy-espaces : http[s]://serveur_tomcat:port_tomcat/espaces/

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