[eeps] Distributed application config file

[PAILLEAU Eric]

Dear all,
I'm not found to be a EEP 'champion' and I don't know if
my proposal can be a EEP or not.
But let me explain my idea, maybe an Erlang specialist can be interested
to be champion on this :

I commonly use distributed application, and I wonder why I need to write
(and backup) a specific config for EACH node, and
do not commit mistakes when dozen(s) of nodes are living together.

My idea is simple : why not removing the current node name in the
'sync_nodes_mandatory' directive, if present before usual process ?

This way, the config file could be same on all nodes (if wanted).

Example with the well known documentation config file :

[{kernel,
  [{distributed, [{myapp, 5000, [cp1@REDACTED, {cp2@REDACTED, cp3@REDACTED}]}]},
   {sync_nodes_mandatory, [cp2@REDACTED, cp3@REDACTED]},
   {sync_nodes_timeout, 5000}
  ]
 }
].

would become on all nodes :

[{kernel,
  [{distributed, [{myapp, 5000, [cp1@REDACTED, {cp2@REDACTED, cp3@REDACTED}]}]},
   {sync_nodes_mandatory, [cp1@REDACTED, cp2@REDACTED, cp3@REDACTED]},
   {sync_nodes_timeout, 5000}
  ]
 }
].

On cp1@REDACTED, the node name would be removed first from
sync_nodes_mandatory list, then continue as usual.
Same on all other nodes.

This would be a very restful enhancement for many people, I guess...
and I don't see any backward problem if implemented...

Regards.