-
New to CCF and trying to migrate an existing setup form 1.0.5 => 4.0.16 the latest release. The start script based on sandbox.sh works fine without any "--config-file" specified. Curated a config_start.json based on a working template. Please let me know if this interpretation is right and if this is not a correct way to start? Thanks Snippet of start command, logs:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
This diff takes care of the issue
|
Beta Was this translation helpful? Give feedback.
-
@bsenthilr is this a migration for a live system, or for a code base/application? If it's the former, you will need to first upgrade to the last 1.x patch, then to 2.0, then to the last 2.x patch etc. Please see Operations compatibility for detail. If it's the latter, you will want to look at the releases notes for 2.0, 3.0 and 4.0 for applicable configuration changes. The I hope this helps, but if not, please do feel free to ask further questions! |
Beta Was this translation helpful? Give feedback.
@bsenthilr is this a migration for a live system, or for a code base/application? If it's the former, you will need to first upgrade to the last 1.x patch, then to 2.0, then to the last 2.x patch etc. Please see Operations compatibility for detail.
If it's the latter, you will want to look at the releases notes for 2.0, 3.0 and 4.0 for applicable configuration changes.
The
--config-file
option to the sandbox only allows overriding the default rpc interface choices otherwise generated. The infrastructure must be able to control other aspects of the config such as file paths, and node to node interfaces, in order to configure a network successfully. Overwriting the config may work for trivi…