Set the local configuration - Fluid Topics - 3.8

Install Fluid Topics on a Single Server

Operating system
Technical Notes

It is necessary to create a local.conf file in order to set the local machine configuration such as the antidot user, etc.

To connect as antidot application user, when prompted, run the following command: su - antidot

  1. Run the following commands:

    As root user

    mkdir -p /usr/local/afs7/setup
    chown antidot:antidot /usr/local/afs7
    chown antidot:antidot /usr/local/afs7/setup

  2. Create the following file:

    As antidot user


Add the following lines:

export AFS7_USER="antidot"
export AFS7_GROUP="antidot"


  • $BACK_OFFICE_HOST is the server hosting the Back Office ("localhost" by default, in singlebox installation).
  • $MY_DATACENTER is the name of the datacenter. Its corresponds to a flag that can be used to group servers to ease their identification. Its default value is AFS Datacenter. Once set, it must never be modified.

The following section explains how user identification works when a KHUB_ADMIN publishes content from Fluid Topics.

Fluid Topics BO user mechanism in FT v3.5

1. A Fluid Topics KHUB_ADMIN user is able to send an archive to Fluid Topics.

The first KHUB_ADMIN user can be created through the root.conf.json file and the User Management interface.

When reaching Fluid Topics, the archive is sent to the Back Office.

2. The archive is then handled by a Back Office user (different from the Fluid Topics one) in order to be sent to the appropriate processing pipelines.

The Back Office user must be set with the MANAGE right and be defined in the local.conf file:

export AFS7_USER="antidot"
export AFS7_GROUP="antidot"

By default, the user antidot with the password change_on_install is already declared in the Back Office with the required rights.

For more information about the Fluid Topics user's login and password, please refer to your Antidot contact.