[docs]: New configuration reference #397
Open
+3,269
−1,770
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
13 tasks
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <a.marcius26@gmail.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
# Conflicts: # src/guide/configure/configuration-types.md # src/reference/torii-endpoints.md
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
outoftardis
reviewed
Feb 26, 2024
| @@ -0,0 +1,5 @@ | |||
| # On-Chain Parameters | |||
|
|
|||
| - These parameters are chain-wide, and each peer should have the same | |||
There was a problem hiding this comment.
Suggested change
| - These parameters are chain-wide, and each peer should have the same | |
| - These parameters are chain-wide, meaning they are the same for each peer. |
| # On-Chain Parameters | ||
|
|
||
| - These parameters are chain-wide, and each peer should have the same | ||
| - It should not be specified in the config file: https://github.com/hyperledger/iroha/issues/4028 |
There was a problem hiding this comment.
Suggested change
| - It should not be specified in the config file: https://github.com/hyperledger/iroha/issues/4028 | |
| - On-chain parameters should not be specified in the config file: https://github.com/hyperledger/iroha/issues/4028 |
outoftardis
reviewed
Feb 26, 2024
|
|
||
| ## Type: Bytes Amount | ||
|
|
||
| Bytes amount is specified as a human-readable string: |
There was a problem hiding this comment.
Suggested change
| Bytes amount is specified as a human-readable string: | |
| The amount of bytes is specified as a human-readable string: |
| value4 = "1GB 5MB" | ||
| ``` | ||
|
|
||
| Iroha can parse sizes in bytes, kilobytes (`K`), megabytes (`M`), gigabytes (`G`), terabytes (`T`), |
There was a problem hiding this comment.
Suggested change
| Iroha can parse sizes in bytes, kilobytes (`K`), megabytes (`M`), gigabytes (`G`), terabytes (`T`), | |
| Iroha can parse sizes in bytes (`B`), kilobytes (`K`), megabytes (`M`), gigabytes (`G`), terabytes (`T`), |
|
|
||
| For more information on socket addresses and networking, refer to the [IANA Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml) or the [RFC 3986](https://tools.ietf.org/html/rfc3986) specification. | ||
|
|
||
| ## Paths Resolution |
There was a problem hiding this comment.
Suggested change
| ## Paths Resolution | |
| ## Path Resolution |
that affects links
There was a problem hiding this comment.
Actually, we can use custom anchors:
# Using custom anchors {#my-anchor}Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
|
@BAStos525, you can preview the migration guide (#481) on the deployment (Reference > Config > Migration): link |
Erigara
reviewed
Apr 5, 2024
| [network] | ||
| address = "localhost:1337" | ||
| ``` | ||
|
|
There was a problem hiding this comment.
I guess new param should go somewhere here:
Suggested change
| ## `network.idle_timeout` {#param-idle-timeout} | |
| - **Type:** String or Number, [Duration](glossary#type-duration) | |
| - **Default:** 60 seconds | |
| Duration of time after which connection with peer is terminated if peer is idle. | |
| ```toml | |
| [network] | |
| idle_timeout = "60s" | |
| ``` |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue: #392
Checklist