# Allow this node to be eligible as a master node (enabled by default): #node.master: true # Allow this node to store data (enabled by default): #node.data: true # You can exploit these settings to design advanced cluster topologies. You can tie this node to a specific name: # node.name: 'pun-essrv01_Logstash' # Every node can be configured to allow or deny being eligible as the master, # and to allow or deny to store the data. # cluster.name: test_cluster # Node # Node names are generated dynamically on startup, so you're relieved # from configuring them manually.

If you're running # multiple clusters on the same network, make sure you're using unique names. # Any element in the configuration can be replaced with environment variables # by placing them in $ # For information on supported formats and syntax for the config file, see # Cluster # Cluster name identifies your cluster for auto-discovery. If you're fine-tuning your cluster, or wondering about the # effect of certain configuration option, please _do ask_ on the # mailing list or IRC channel. # Most of the time, these defaults are just fine for running a production # cluster. # Elasticsearch comes with reasonable defaults for most settings, # so you can try it out without bothering with configuration. # The installation procedure is covered at #. Application developers should # consult the guide at. Elasticsearch/config/elasticsearch.yml:/etc/elasticsearch/config/elasticsearch.yml tty : true Redis: image: redis:latest ports: - '6379:6379' volumes: - /Redis/nf:/var/lib/redis restart: alwaysДў: elasticsearch.yml # Elasticsearch Configuration Example # This file contains an overview of various configuration settings, # targeted at operations staff. Elasticsearch/data:/var/lib/elasticsearch.

Docker for mac access container