Do not hardcode the numbers of sync nodes

[hellodword]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing requests and didn't find any that were similar
• I have considered creating a pull request instead and want to proceed

Clear and concise description of the problem

any-sync-dockercompose/.env.common

Lines 22 to 38 in 9609edf

	ANY_SYNC_NODE_1_HOST=any-sync-node-1
	ANY_SYNC_NODE_1_PORT=1001
	ANY_SYNC_NODE_1_ADDRESSES=${ANY_SYNC_NODE_1_HOST}:${ANY_SYNC_NODE_1_PORT}
	ANY_SYNC_NODE_1_QUIC_PORT=1011
	ANY_SYNC_NODE_1_QUIC_ADDRESSES=${ANY_SYNC_NODE_1_HOST}:${ANY_SYNC_NODE_1_QUIC_PORT}
	ANY_SYNC_NODE_2_HOST=any-sync-node-2
	ANY_SYNC_NODE_2_PORT=1002
	ANY_SYNC_NODE_2_ADDRESSES=${ANY_SYNC_NODE_2_HOST}:${ANY_SYNC_NODE_2_PORT}
	ANY_SYNC_NODE_2_QUIC_PORT=1012
	ANY_SYNC_NODE_2_QUIC_ADDRESSES=${ANY_SYNC_NODE_2_HOST}:${ANY_SYNC_NODE_2_QUIC_PORT}
	ANY_SYNC_NODE_3_HOST=any-sync-node-3
	ANY_SYNC_NODE_3_PORT=1003
	ANY_SYNC_NODE_3_ADDRESSES=${ANY_SYNC_NODE_3_HOST}:${ANY_SYNC_NODE_3_PORT}
	ANY_SYNC_NODE_3_QUIC_PORT=1013
	ANY_SYNC_NODE_3_QUIC_ADDRESSES=${ANY_SYNC_NODE_3_HOST}:${ANY_SYNC_NODE_3_QUIC_PORT}

any-sync-dockercompose/docker-generateconfig/anyconf.sh

Lines 33 to 35 in 9609edf

	--t tree \
	--t tree \
	--t tree \

any-sync-dockercompose/docker-generateconfig/anyconf.sh

Lines 39 to 41 in 9609edf

	--addresses ${ANY_SYNC_NODE_1_ADDRESSES} \
	--addresses ${ANY_SYNC_NODE_2_ADDRESSES} \
	--addresses ${ANY_SYNC_NODE_3_ADDRESSES} \

any-sync-dockercompose/docker-generateconfig/anyconf.sh

Lines 55 to 56 in 9609edf

	yq --indent 2 --inplace ".account.signingKey |= \"${NETWORK_SIGNING_KEY}\"" account3.yml
	yq --indent 2 --inplace ".account.signingKey |= \"${NETWORK_SIGNING_KEY}\"" account5.yml

any-sync-dockercompose/docker-generateconfig/processing.sh

Line 29 in 9609edf

for i in {0..2}; do

any-sync-dockercompose/docker-generateconfig/processing.sh

Lines 39 to 46 in 9609edf

	cat "${NETWORK_FILE}" docker-generateconfig/etc/common.yml storage/docker-generateconfig/account3.yml docker-generateconfig/etc/coordinator.yml \
	> ${DEST_PATH}/any-sync-coordinator/config.yml
	echo "INFO: Generate config files for filenode"
	cat "${NETWORK_FILE}" docker-generateconfig/etc/common.yml storage/docker-generateconfig/account4.yml docker-generateconfig/etc/filenode.yml \
	> ${DEST_PATH}/any-sync-filenode/config.yml
	echo "INFO: Generate config files for consensusnode"
	cat "${NETWORK_FILE}" docker-generateconfig/etc/common.yml storage/docker-generateconfig/account5.yml docker-generateconfig/etc/consensusnode.yml \
	> ${DEST_PATH}/any-sync-consensusnode/config.yml

Suggested solution

I'm not sure, maybe jinja2 is a good choice?

Alternative

No response

Additional context

No response

[fb929]

this will be too complicated: as it will also require simultaneous templating of docker-compose.yml files, .env, and the generator, along with post-processing configurations.
moreover, this does not align with the goals of this repository

[hellodword]

I think it is already too complicated. There are too many shell scripts and Python scripts, and hardcoding makes customization difficult.

Furthermore, are three nodes by default necessary for self-hosted and all-in-one users? Are there any design reasons for this?

Meanwhile, env.py and setListenIp.py are dynamic, they're good starts for removing hardcodings:

any-sync-dockercompose/docker-generateconfig/setListenIp.py

Lines 57 to 61 in 82b9ec1

	for name,value in envVars.items():
	if re.match(r"^(ANY_SYNC_.*_PORT)$", name) and value == listenPort:
	if re.match(r"^(ANY_SYNC_.*_QUIC_PORT)$", name):
	# skip port, if PORT == QUIC_PORT
	continue

[fb929]

The minimum number of any-sync-nodes required for the cluster to operate is 3.
Increasing this number is not practical because, architecturally, self-hosted can only operate within a single docker-host.
Additionally, at the moment, any-sync-node does not support rebalancing - you cannot change the number of nodes in an existing cluster, as this will lead to errors and potential data loss.