docker.elastic.co/elasticsearch/elasticsearch:7.17.5 environment: - discovery.type=single-node ports: - 9200:9200 unomi: # Unomi version can be updated based on your needs Initializing user list service endpoint... Initializing geonames service endpoint... Initializing segment service endpoint... Initializing scoring service endpoint... Initializing campaigns service endpoint and for any standalone Elasticsearch nodes you will need to open the following ports for proper node- to-node communication : 9200 (Elasticsearch REST API), 9300 (Elasticsearch TCP transport) Of course

profiles or sessions subdirectory then directory Rule rules Scoring scorings Segment segments Tag tags ValueType values Blueprint is used to declare what the plugin provides and inject SEGMENTS `Segment`s represent dynamically evaluated groups of similar profiles in order to categorize the associated users. To be considered part of a given segment, users must satisfies the segment’s condition condition. If they match, users are automatically added to the segment. Similarly, if at any given point during, they cease to satisfy the segment’s condition, they are automatically removed from it. TAG

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 8.11. Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initializing user list service endpoint... Initializing geonames service endpoint... Initializing segment service endpoint... Initializing scoring service endpoint... Initializing campaigns service endpoint and for any standalone Elasticsearch nodes you will need to open the following ports for proper node-to-node communication : 9200 (Elasticsearch REST API), 9300 (Elasticsearch TCP transport) Of course