For each feed/page/channel/etc, Fairpost uses one 'user' that has it's own configuration, logging and feed folder. If you don't specify a user, Fairpost assumes it's 'admin'. The admin user has no homedir and uses global config, logging and storage.
Both the global .env and the user .env will be read. The users .env can override anything from the global config, but likely, you only want to enter the feed/page/channel/etc settings for each platform. The rest is set globally.
The other stores, like access tokens, will also be stored in the user directory in the path specified in his .env
When command are called on behalf of a user, ./log4js.json uses the
'user' category instead of the default category. It logs in a dedicated
logfile for the user, but also append some messages to the global log.
The user could also host it's own log4js.json; settings there would completely override the settings in the global log4j.json.