Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel62
outlinefalse
styledisc
typelist
printabletrue

...

General Installation Instructions

1. Install Docker

  • For Mac and Windows: Install Docker Desktop and launch it.

  • For Linux: Ensure the Docker service is running. Verify by using:

Code Block
languagebash
sudo services docker status

2. Verify Docker Compose

  • Make sure Docker Compose is installed. Run:

Code Block
languagebash
docker compose version

...

Code Block
languagebash
docker network ls
  • You should see a result like:

Code Block
languagedocker
NETWORK ID     NAME                    DRIVER    SCOPE
06e4817f8b43   apliqo-core             bridge    local

...

Code Block
languagedocker
docker logs ${docker_container_id}

9. Access Apliqo UX

  • Once the containers are running, navigate to the following URL in your browser: http://your-ip-address
    By default, the interface will be accessible from port 80.

...

Environment Variables

...

Variable

Description

Default Value

Required

Notes

PORT

...

Port on which the backend server

...

runs inside the

...

Docker container.

...

4000

No

PORT_EXPOSE

...

Port on which the backend server is accessible from machine IP.

...

Docker

...

bridges PORT and PORT_EXPOSE.

...

4000

...

No

JWT_SECRET

...

...

A secret string

...

for encrypting access tokens. Ensure it is unique and secure.

None

Yes

There is no default value, set the arbitrary string or generate some random string.

SERVICE_USER_PASSWORD

...

colourRed
titlerequired

...

Password for default system user which could be used on first install.

...

After the backend service first starts, you will be able to login into the app via:

...

username:

...

service-admin

...


password:

...

SERVICE_USER_PASSWORD

None

...

Yes

Password for service user stores as a hashed string by bcryptjs. After user creation in mongodb you may remove this password from .env.

...

DB

...

_NAME

...

Apliqo Content Store database name in MongoDB server.

...

apliqo-content-store

No

DB_HOST

...

MongoDB server's domain name or IP address

...

.

apliqo-mongo

...

No

Inside the docker network, container names could be used as domain names to access the resource. If you are not using Docker for MongoDB database, set IP address or domain name as the value for this variable.

DB_PORT

...

MongoDB server's port.

...

27017

No

MONGO_DB_PORT_EXPOSE

...

...

Port on the machine where docker is running to access the MongoDB.
Set this variable to have an ability to access MongoDB from outside the docker network and to manage the DB by GUI tools (Mongo Compass, Studio 3T)

None

Yes

DB_USER

...

colourRed
titlerequired

...

Username of a root user from which account would be created a connection to the MongoDB.

None

Yes

DB_PASSWORD

...

...

Password of a root user from which account would be created a connection to the MongoDB.

None

...

Yes

If you are using default Apliqo UX setup. On first install DB_USER and DB_PASSWORD would be used to create a MongoDB user to access the database. This user would be stored in admin database by default.

DB_CONNECTION_SCHEME

Description: MongoDB uses a connection variant.
There are 2 options:

mongodb - Standard Connection String Format. The standard format of the MongoDB connection URI is used to connect to a MongoDB deployment: standalone, replica set, or a sharded cluster.

mongodb+srv - DNS Seed List Connection Format. The +srv indicates to the client that the hostname that follows corresponds to a DNS SRV record.

...

mongodb

...

No

If you don't have your dedicated MongoDB server - use the default value.

DB_AUTHSOURCE

...

Database inside MongoDB server which stores users and their permission in MongoDB.

...

admin

...

No

REDIS_HOST

...

Hostname for the Redis database

...

, used for caching and queues.

...

apliqo-redis

...

No

Inside the docker network, container names could be used as domain names to access the resource. If you are not using Docker for Redis database, set IP address or domain name as value for this variable.

...

TM1_VERIFY_SSL

...

Variable to control the SSL verification for all TM1 API requests.

...

Available values: 0 or 1
Set 1 if you want to enable the TM1 API SSL verification.
Set 0 if you want to disable the TM1 API SSL verification. (Could be used for TM1 with self-signed

...

certificate)

...

0

No

...

Troubleshooting

» MacOS with M1 chip peculiarities

The architecture of the M1 chip is not fully compatible with the architecture of containers that are used in docker. In this case, you need to install a couple of things to make everything work correctly for your environment.

Rosetta

First of all, you need to install Rosetta and turn the terminal into rosetta mode. If you're using a Mac with the M1 chip, some additional steps are required to ensure compatibility:

Rosetta

1. Install Rosetta

Code Block
softwareupdate --install-rosetta --agree-to-license

It seems to be a good idea to run your entire Terminal in Rosetta2. Enable Rosetta for Terminal:

  • Go to Finder > Applications and find your > Terminal

  • Right-Click "Terminal" > Get Info > Enable click ‘Terminal’ and select Get Info

  • Check the box "Open using Rosetta."

  • Click to Open the Terminal, type arch to verify it says Terminal and verify it’s running under Rosetta by typing:

Code Block
arch
  • It should return i386 or x86_64 now.

DockerFor

  • Ensure Docker Desktop

...

  • is usingVirtioFS as a Virtualization framework

...

  • in general settings for improved I/O performance for operations on bind mounts.

  • For containers

...

  • that

...

  • require the AMD architecture, add the following line to

...

  • the container configuration:

Code Block
platform: linux/amd64

...