You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 7, 2019. It is now read-only.
All members of a replica set require the same keyfile for encrypted/authenticated communication between replica nodes. That file is currently static in this repo and copied over on container build. Ideally, key generation would happen at build time. The main reason the pre-generated keyfile is included as a static file now is because each member of a set could potentially be built at different times, so random key generators at build time aren't an option. The key needs to match on every node in a set, so environment variables seem to be the simplest way to keep them in sync while also keeping the ability to be unique.
Maybe set it up to use env vars to set the key and then just handle the random key generation in Launchdock?
All members of a replica set require the same keyfile for encrypted/authenticated communication between replica nodes. That file is currently static in this repo and copied over on container build. Ideally, key generation would happen at build time. The main reason the pre-generated keyfile is included as a static file now is because each member of a set could potentially be built at different times, so random key generators at build time aren't an option. The key needs to match on every node in a set, so environment variables seem to be the simplest way to keep them in sync while also keeping the ability to be unique.
Maybe set it up to use env vars to set the key and then just handle the random key generation in Launchdock?