Request for Production Configuration Files about quack HOT 1 CLOSED

Hi Bob,

With the schema above your current configuration will change insignificantly.

1. First, you'll have to point your config to a Mongo replica set. It could be either a list of hosts (in that case Driver will auto-detect the master node) or a connection URI (e.g., if you set up Mongo using mongo cloud https://www.mongodb.com/cloud/)

so either
mongo.replicaSet=MONGO_HOST_IP1:27017,MONGO_HOST_IP2:27017,MONGO_HOST_IP3:27017
or
mongo.uri=mongodb+srv://some_uri_given_you_by_mongo_provider_or_your_local_dba

2. Second, you'll have to set up Hazelcast Session Provider. It will allow all your quack instanced share authenticated users sessions

whoru.session.provider=ru.greatbit.whoru.auth.providers.HazelcastSessionProvider

These are optional - use default values as stated below:
hazelcast.group.name=dev
hazelcast.group.password=dev-pass
hazelcast.ttl.sec=1209600
hazelcast.port=5903
hazelcast.port.rest=5904
hazelcast.port.auto.increment=true
hazelcast.backup.count=1
hazelcast.prefer.ipv4.stack=true

If you know IP addresses of all QuAck instances your are running - just list them comma separated here:
hazelcast.members=IP_ADDRESS_1,IPADDRESS_2,IPADDRESS_3
hazelcast.interface=127.0.0.1

If you have a dynamic IP addresses range (e.g. - private VPC) - you can configure an auto-discovery like (in this example VPC has range 10.0.0.0. 10.0.255.255)
hazelcast.members=127.0.0.1
hazelcast.interface=10.0...

from quack.