diff --git a/content/concepts/consensus-network/amendments/amendments.md b/content/concepts/consensus-network/amendments/amendments.md index 352550b8fe..447d81839e 100644 --- a/content/concepts/consensus-network/amendments/amendments.md +++ b/content/concepts/consensus-network/amendments/amendments.md @@ -229,7 +229,7 @@ TrustSetAuth After an amendment has become enabled, it can never be disabled. (To reverse protocol changes, it would be necessary to create a new amendment.) However, separate ledger chains, such as [test networks](parallel-networks.html) or [stand-alone mode](rippled-server-modes.html#stand-alone-mode) can have different sets of amendments applied. Therefore, the pre-amendment code may continue to run in those cases, and the software must work with an increasing number of combinations of amendments that may or may not be enabled on any given test network. -Rather than maintain the source code for all old behavior indefinitely, [XRP Ledger Standard 11d](https://github.com/XRPLF/XRPL-Standards/discussions/19) defines a process for retiring the pre-amendment code. In this process, amendments that have been enabled on the XRP Ledger Mainnet can have the pre-amendment code removed, making them apply unconditionally as part of the XRP Ledger protocol. For the XRP Ledger's [reference server implementation](the-rippled-server.html), the developers periodically chooses a cutoff date **at least 2 years** in the past, and retire pre-amendment source code for amendments that were enabled on the network before the cutoff date. +Rather than maintain the source code for all old behavior indefinitely, [XRP Ledger Standard 11d](https://github.com/XRPLF/XRPL-Standards/discussions/19) defines a process for retiring the pre-amendment code. In this process, amendments that have been enabled on the XRP Ledger Mainnet can have the pre-amendment code removed, making them apply unconditionally as part of the XRP Ledger protocol. For the XRP Ledger's [reference server implementation](xrpl-servers.html), the developers periodically chooses a cutoff date **at least 2 years** in the past, and retire pre-amendment source code for amendments that were enabled on the network before the cutoff date. When pre-amendment code has been retired, the server follows the amended logic for all transactions at all times. As a result, the server is no longer guaranteed to produce historically-accurate results if you try to replay ledgers older than the cutoff date. The server prints a warning if you try to [load and replay a ledger](load-a-saved-ledger-in-stand-alone-mode.html) that is older than the cutoff date. To produce historically-accurate results, you must compile or download an old server binary that has the legacy code. diff --git a/content/concepts/consensus-network/consensus.ja.md b/content/concepts/consensus-network/consensus.ja.md index 3ba103cb6b..597464691b 100644 --- a/content/concepts/consensus-network/consensus.ja.md +++ b/content/concepts/consensus-network/consensus.ja.md @@ -62,7 +62,7 @@ _図3: レジャーバージョンに適用されるトランザクション_ ## XRP Ledgerプロトコル - コンセンサスと検証 -ピアツーピアのXRP Ledgerネットワークは、トランザクションを承認して処理する多数の独立したXRP Ledgerサーバー（通常、[`rippled`](the-rippled-server.html)を実行）で構成されています。クライアントアプリケーションは、トランザクションに署名してXRP Ledgerサーバーに送信します。サーバーは、これらの候補トランザクションを処理するためにネットワーク内を中継します。クライアントアプリケーションには、モバイルおよびウェブウォレット、金融機関へのゲートウェイ、電子取引プラットフォームなどがあります。 +ピアツーピアのXRP Ledgerネットワークは、トランザクションを承認して処理する多数の独立したXRP Ledgerサーバー（通常、[`rippled`](xrpl-servers.html)を実行）で構成されています。クライアントアプリケーションは、トランザクションに署名してXRP Ledgerサーバーに送信します。サーバーは、これらの候補トランザクションを処理するためにネットワーク内を中継します。クライアントアプリケーションには、モバイルおよびウェブウォレット、金融機関へのゲートウェイ、電子取引プラットフォームなどがあります。 [![図4: XRP Ledgerプロトコルの参加者](img/xrp-ledger-network.ja.png)](img/xrp-ledger-network.ja.png) diff --git a/content/concepts/consensus-network/consensus.md b/content/concepts/consensus-network/consensus.md index 4e53b82efa..c073d42a5b 100644 --- a/content/concepts/consensus-network/consensus.md +++ b/content/concepts/consensus-network/consensus.md @@ -62,7 +62,7 @@ Important: Some [`rippled` APIs](rippled-api.html) provide provisional results, ## The XRP Ledger Protocol – Consensus and Validation -The peer-to-peer XRP Ledger network consists of many independent XRP Ledger servers (typically running [`rippled`](the-rippled-server.html)) that accept and process transactions. Client applications sign and send transactions to XRP Ledger servers, which relay these candidate transactions throughout the network for processing. Examples of client applications include mobile and web wallets, gateways to financial institutions, and electronic trading platforms. +The peer-to-peer XRP Ledger network consists of many independent XRP Ledger servers (typically running [`rippled`](xrpl-servers.html)) that accept and process transactions. Client applications sign and send transactions to XRP Ledger servers, which relay these candidate transactions throughout the network for processing. Examples of client applications include mobile and web wallets, gateways to financial institutions, and electronic trading platforms. {{ include_svg("img/xrp-ledger-network.svg", "Figure 4: Participants in the XRP Ledger Protocol") }} diff --git a/content/concepts/consensus-network/federated-sidechains.ja.md b/content/concepts/consensus-network/federated-sidechains.ja.md index bbf9a966dc..385ad6056a 100644 --- a/content/concepts/consensus-network/federated-sidechains.ja.md +++ b/content/concepts/consensus-network/federated-sidechains.ja.md @@ -51,7 +51,7 @@ _レスポンス トランザクション_: トリガーとなるトランザク ## フェデレーションサイドチェーンのセットアップ方法 -フェデレーションサイドチェーンは現在開発者プレビューとして提供されているため、サイドチェーンの可能性を実験的に探ることができます。メインチェーンネットワーク内の[サーバー](the-rippled-server.html)のバージョンが1.8.0以上であれば、サイドチェーンをXRP Ledger Testnet、Devnet、Mainnetに接続することができます。 +フェデレーションサイドチェーンは現在開発者プレビューとして提供されているため、サイドチェーンの可能性を実験的に探ることができます。メインチェーンネットワーク内の[サーバー](xrpl-servers.html)のバージョンが1.8.0以上であれば、サイドチェーンをXRP Ledger Testnet、Devnet、Mainnetに接続することができます。 **注意:** サイドチェーンをXRP Ledger Mainnetに接続することで、少量の開発やテストを行うことができますが、フェデレーションサイドチェーンがリリースされるまでは、本番環境での使用はお勧めできません。 diff --git a/content/concepts/consensus-network/federated-sidechains.md b/content/concepts/consensus-network/federated-sidechains.md index 3607732b88..7c3ae7eabe 100644 --- a/content/concepts/consensus-network/federated-sidechains.md +++ b/content/concepts/consensus-network/federated-sidechains.md @@ -51,7 +51,7 @@ _Triggering transaction_: A transaction that causes the federators to start the ## How to Set Up a Federated Sidechain -Federated Sidechains are currently available as an Engineering Preview so you can experiment and explore the potential of sidechains. You can connect sidechains to the XRP Ledger Testnet, Devnet, or Mainnet as long as [the servers](the-rippled-server.html) in the mainchain network are running version 1.8.0 or higher. +Federated Sidechains are currently available as an Engineering Preview so you can experiment and explore the potential of sidechains. You can connect sidechains to the XRP Ledger Testnet, Devnet, or Mainnet as long as [the servers](xrpl-servers.html) in the mainchain network are running version 1.8.0 or higher. **Caution:** You can connect sidechains to the XRP Ledger Mainnet to develop and test with small amounts; it is not recommended for production use cases until federated sidechains are available in a release. diff --git a/content/concepts/introduction/software-ecosystem.ja.md b/content/concepts/introduction/software-ecosystem.ja.md index 97f296d665..6434ab59ef 100644 --- a/content/concepts/introduction/software-ecosystem.ja.md +++ b/content/concepts/introduction/software-ecosystem.ja.md @@ -22,7 +22,7 @@ XRP Ledgerは、「価値のインターネット」を推進および実現可 ### rippled: コアサーバー -XRP Ledgerの中心であるピアツーピアネットワークは、コンセンサスとトランザクションプロセスのルールを実行するために、信頼性が高く、効率のよいサーバーを必要とします。Rippleでは、このサーバーソフトウェアのリファレンス実装である[**`rippled`**](the-rippled-server.html)（発音は「リップルディー」）を管理および公開しています。このサーバーは、[一般利用が可能なオープンソースライセンス](https://github.com/ripple/rippled/blob/develop/LICENSE.md)の下で使用できるため、誰でもこのサーバーの自身のインスタンスを検証し、変更することができます。また、いくつかの制限の下でそれを再公開することができます。 +XRP Ledgerの中心であるピアツーピアネットワークは、コンセンサスとトランザクションプロセスのルールを実行するために、信頼性が高く、効率のよいサーバーを必要とします。Rippleでは、このサーバーソフトウェアのリファレンス実装である[**`rippled`**](xrpl-servers.html)（発音は「リップルディー」）を管理および公開しています。このサーバーは、[一般利用が可能なオープンソースライセンス](https://github.com/ripple/rippled/blob/develop/LICENSE.md)の下で使用できるため、誰でもこのサーバーの自身のインスタンスを検証し、変更することができます。また、いくつかの制限の下でそれを再公開することができます。 `rippled`の各インスタンスは、（[Test Netなどの並列ネットワーク](parallel-networks.html)に従うように構成されていない限り）同じネットワークに同期され、ネットワーク全体のあらゆる通信にアクセスできます。ネットワーク上の各`rippled`サーバーは、最近のトランザクションの一部と、それらのトランザクションで行われた変更の記録とともに、XRP Ledger全体の最新の状態データの完全なコピーを保持します。また、各サーバーは各トランザクションを単独で処理すると同時に、そのトランザクションの結果が残りのネットワークに一致するか検証します。サーバーは、より多くの[レジャー履歴](ledger-history.html)を保持したり、[バリデータ](rippled-server-modes.html#バリデータを運用する理由)としてコンセンサスプロセスに参加するように構成することができます。 diff --git a/content/concepts/introduction/software-ecosystem.md b/content/concepts/introduction/software-ecosystem.md index b14132f099..1264243415 100644 --- a/content/concepts/introduction/software-ecosystem.md +++ b/content/concepts/introduction/software-ecosystem.md @@ -24,7 +24,7 @@ The XRP Ledger is home to a deep, layered ecosystem of software projects powerin ### rippled: The Core Server -The peer-to-peer network at the heart of the XRP Ledger requires a highly-reliable, efficient server to enforce the rules of consensus and transaction processing. Ripple manages and publishes a reference implementation of this server software, called [**`rippled`**](the-rippled-server.html) (pronounced "ripple-dee"). The server is available under [a permissive open-source license](https://github.com/ripple/rippled/blob/develop/LICENSE.md), so anyone can inspect and modify their own instance of the server, and re-publish with few restrictions. +The peer-to-peer network at the heart of the XRP Ledger requires a highly-reliable, efficient server to enforce the rules of consensus and transaction processing. Ripple manages and publishes a reference implementation of this server software, called [**`rippled`**](xrpl-servers.html) (pronounced "ripple-dee"). The server is available under [a permissive open-source license](https://github.com/ripple/rippled/blob/develop/LICENSE.md), so anyone can inspect and modify their own instance of the server, and re-publish with few restrictions. Every instance of `rippled` syncs to the same network (unless it's configured to follow a [parallel network such as a test net](parallel-networks.html)) and has access to all communications across the network. Every `rippled` server on the network keeps a complete copy of the latest state data for the entire XRP Ledger, along with a slice of recent transactions and a record of the changes those transactions made, and every server processes every transaction independently while verifying that its outcome matches the rest of the network. Servers can be configured to keep more [ledger history](ledger-history.html) and to participate in the consensus process as a [validator](rippled-server-modes.html#validators). diff --git a/content/concepts/payment-system-basics/transaction-basics/transaction-basics.md b/content/concepts/payment-system-basics/transaction-basics/transaction-basics.md index 49cd899b60..f3acc9c3ce 100644 --- a/content/concepts/payment-system-basics/transaction-basics/transaction-basics.md +++ b/content/concepts/payment-system-basics/transaction-basics/transaction-basics.md @@ -59,7 +59,7 @@ Sending a transaction to the XRP Ledger involves several steps: 1. Create an [unsigned transaction in JSON format](#example-unsigned-transaction). 2. Use one or more signatures to [authorize the transaction](#authorizing-transactions). -3. Submit a transaction to an XRP Ledger server (usually a [`rippled` instance](the-rippled-server.html)). If the transaction is properly formed, the server provisionally applies the transaction to its current version of the ledger and relays the transaction to other members of the peer-to-peer network. +3. Submit a transaction to an XRP Ledger server (usually a [`rippled` instance](xrpl-servers.html)). If the transaction is properly formed, the server provisionally applies the transaction to its current version of the ledger and relays the transaction to other members of the peer-to-peer network. 4. The [consensus process](consensus.html) determines which provisional transactions get included in the next validated ledger. 5. The servers apply those transactions to the previous ledger in a canonical order and share their results. 6. If enough [trusted validators](rippled-server-modes.html#validators) created the exact same ledger, that ledger is declared _validated_ and the [results of the transactions](transaction-results.html) in that ledger are immutable. diff --git a/content/concepts/the-rippled-server/clustering.ja.md b/content/concepts/xrpl-servers/clustering.ja.md similarity index 98% rename from content/concepts/the-rippled-server/clustering.ja.md rename to content/concepts/xrpl-servers/clustering.ja.md index e536356bea..fa4d6109eb 100644 --- a/content/concepts/the-rippled-server/clustering.ja.md +++ b/content/concepts/xrpl-servers/clustering.ja.md @@ -1,6 +1,6 @@ --- html: clustering.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: 暗号処理の負荷を分散させるためにクラスターでrippledサーバーを運用できます。 labels: - コアサーバー diff --git a/content/concepts/the-rippled-server/clustering.md b/content/concepts/xrpl-servers/clustering.md similarity index 97% rename from content/concepts/the-rippled-server/clustering.md rename to content/concepts/xrpl-servers/clustering.md index f1afdecd5e..3bc9acbf91 100644 --- a/content/concepts/the-rippled-server/clustering.md +++ b/content/concepts/xrpl-servers/clustering.md @@ -1,6 +1,6 @@ --- html: clustering.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: Run rippled servers in a cluster to share the load of cryptography between them. labels: - Core Server diff --git a/content/concepts/the-rippled-server/ledger-history/history-sharding.ja.md b/content/concepts/xrpl-servers/ledger-history/history-sharding.ja.md similarity index 100% rename from content/concepts/the-rippled-server/ledger-history/history-sharding.ja.md rename to content/concepts/xrpl-servers/ledger-history/history-sharding.ja.md diff --git a/content/concepts/the-rippled-server/ledger-history/history-sharding.md b/content/concepts/xrpl-servers/ledger-history/history-sharding.md similarity index 100% rename from content/concepts/the-rippled-server/ledger-history/history-sharding.md rename to content/concepts/xrpl-servers/ledger-history/history-sharding.md diff --git a/content/concepts/the-rippled-server/ledger-history/ledger-history.ja.md b/content/concepts/xrpl-servers/ledger-history/ledger-history.ja.md similarity index 95% rename from content/concepts/the-rippled-server/ledger-history/ledger-history.ja.md rename to content/concepts/xrpl-servers/ledger-history/ledger-history.ja.md index 22f9e73fa1..4cd4fbc154 100644 --- a/content/concepts/the-rippled-server/ledger-history/ledger-history.ja.md +++ b/content/concepts/xrpl-servers/ledger-history/ledger-history.ja.md @@ -1,6 +1,6 @@ --- html: ledger-history.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: rippledサーバーはトランザクションの変動金額と状態の履歴をローカルに保管します。 labels: - データ保持 @@ -9,7 +9,7 @@ labels: --- # レジャー履歴 -[コンセンサスプロセス](intro-to-consensus.html)により、[検証済みレジャーバージョン](ledgers.html)のチェーンが作成されます。各バージョンは、以前のバージョンに[トランザクション](transaction-basics.html)のセットを適用して生成されます。各[`rippled`サーバー](the-rippled-server.html)には、レジャーバージョンとトランザクション履歴がローカルに保管されます。サーバーに保管されるトランザクション履歴の量は、サーバーがオンラインであった期間と、サーバーが取得し、保持する履歴量の設定に応じて異なります。 +[コンセンサスプロセス](intro-to-consensus.html)により、[検証済みレジャーバージョン](ledgers.html)のチェーンが作成されます。各バージョンは、以前のバージョンに[トランザクション](transaction-basics.html)のセットを適用して生成されます。各[`rippled`サーバー](xrpl-servers.html)には、レジャーバージョンとトランザクション履歴がローカルに保管されます。サーバーに保管されるトランザクション履歴の量は、サーバーがオンラインであった期間と、サーバーが取得し、保持する履歴量の設定に応じて異なります。 ピアツーピアのXRP Ledgerネットワーク内のサーバーは、コンセンサスプロセスの一環としてトランザクションやその他のデータを相互に共有します。各サーバーは個別に新しいレジャーバージョンを作成し、その結果を信頼できるバリデータと比較して、整合性を維持します。（信頼できるバリデータのコンセンサスがサーバーの結果と一致しない場合は、サーバーがピアから必要なデータを取得して整合性を維持します。）サーバーはピアから古いデータをダウンロードして、利用可能な履歴のギャップを埋めることができます。レジャーはデータの暗号[ハッシュ](basic-data-types.html#ハッシュ)を使用した構造となっているため、すべてのサーバーがデータの整合性の検証を行えます。 diff --git a/content/concepts/the-rippled-server/ledger-history/ledger-history.md b/content/concepts/xrpl-servers/ledger-history/ledger-history.md similarity index 96% rename from content/concepts/the-rippled-server/ledger-history/ledger-history.md rename to content/concepts/xrpl-servers/ledger-history/ledger-history.md index 868e17aa9d..1b7496033c 100644 --- a/content/concepts/the-rippled-server/ledger-history/ledger-history.md +++ b/content/concepts/xrpl-servers/ledger-history/ledger-history.md @@ -1,6 +1,6 @@ --- html: ledger-history.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: rippled servers store a variable amount of transaction and state history locally. labels: - Data Retention @@ -9,7 +9,7 @@ labels: --- # Ledger History -The [consensus process](intro-to-consensus.html) creates a chain of [validated ledger versions](ledgers.html), each derived from the previous one by applying a set of [transactions](transaction-basics.html). Every [`rippled` server](the-rippled-server.html) stores ledger versions and transaction history locally. The amount of transaction history a server stores depends on how long that server has been online and how much history it is configured to fetch and keep. +The [consensus process](intro-to-consensus.html) creates a chain of [validated ledger versions](ledgers.html), each derived from the previous one by applying a set of [transactions](transaction-basics.html). Every [`rippled` server](xrpl-servers.html) stores ledger versions and transaction history locally. The amount of transaction history a server stores depends on how long that server has been online and how much history it is configured to fetch and keep. Servers in the peer-to-peer XRP Ledger network share transactions and other data with each other as part of the consensus process. Each server independently builds each new ledger version and compares results with its trusted validators to ensure consistency. (If a consensus of trusted validators disagrees with a server's results, that server fetches the necessary data from its peers to achieve consistency.) Servers can download older data from their peers to fill gaps in their available history. The structure of the ledger uses cryptographic [hashes](basic-data-types.html#hashes) of the data so that any server can verify the integrity and consistency of the data. diff --git a/content/concepts/the-rippled-server/ledger-history/online-deletion.ja.md b/content/concepts/xrpl-servers/ledger-history/online-deletion.ja.md similarity index 100% rename from content/concepts/the-rippled-server/ledger-history/online-deletion.ja.md rename to content/concepts/xrpl-servers/ledger-history/online-deletion.ja.md diff --git a/content/concepts/the-rippled-server/ledger-history/online-deletion.md b/content/concepts/xrpl-servers/ledger-history/online-deletion.md similarity index 100% rename from content/concepts/the-rippled-server/ledger-history/online-deletion.md rename to content/concepts/xrpl-servers/ledger-history/online-deletion.md diff --git a/content/concepts/the-rippled-server/peer-protocol.ja.md b/content/concepts/xrpl-servers/peer-protocol.ja.md similarity index 99% rename from content/concepts/the-rippled-server/peer-protocol.ja.md rename to content/concepts/xrpl-servers/peer-protocol.ja.md index ac456736d7..075d60ac16 100644 --- a/content/concepts/the-rippled-server/peer-protocol.ja.md +++ b/content/concepts/xrpl-servers/peer-protocol.ja.md @@ -1,6 +1,6 @@ --- html: peer-protocol.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: ピアプロトコルは、rippledサーバーが互いに通信する言語を指定します。 labels: - コアサーバー diff --git a/content/concepts/the-rippled-server/peer-protocol.md b/content/concepts/xrpl-servers/peer-protocol.md similarity index 99% rename from content/concepts/the-rippled-server/peer-protocol.md rename to content/concepts/xrpl-servers/peer-protocol.md index 5bb8fe006c..d5f8da8175 100644 --- a/content/concepts/the-rippled-server/peer-protocol.md +++ b/content/concepts/xrpl-servers/peer-protocol.md @@ -1,6 +1,6 @@ --- html: peer-protocol.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: The peer protocol specifies the language rippled servers speak to each other. labels: - Core Server diff --git a/content/concepts/the-rippled-server/rippled-server-modes.ja.md b/content/concepts/xrpl-servers/rippled-server-modes.ja.md similarity index 99% rename from content/concepts/the-rippled-server/rippled-server-modes.ja.md rename to content/concepts/xrpl-servers/rippled-server-modes.ja.md index 038386e9d8..bf50546202 100644 --- a/content/concepts/the-rippled-server/rippled-server-modes.ja.md +++ b/content/concepts/xrpl-servers/rippled-server-modes.ja.md @@ -1,6 +1,6 @@ --- html: rippled-server-modes.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: ストックサーバー、バリデータサーバー、スタンドアロンモードで運用されるrippledサーバーなど、rippledサーバーのモードについて説明します。 labels: - コアサーバー diff --git a/content/concepts/the-rippled-server/rippled-server-modes.md b/content/concepts/xrpl-servers/rippled-server-modes.md similarity index 98% rename from content/concepts/the-rippled-server/rippled-server-modes.md rename to content/concepts/xrpl-servers/rippled-server-modes.md index 4e7b8193c6..e05c637712 100644 --- a/content/concepts/the-rippled-server/rippled-server-modes.md +++ b/content/concepts/xrpl-servers/rippled-server-modes.md @@ -1,6 +1,6 @@ --- html: rippled-server-modes.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: Learn about rippled server modes, including stock servers, validator servers, and rippled servers run in stand-alone mode. labels: - Core Server @@ -36,7 +36,7 @@ P2P Mode servers connect to [Mainnet](parallel-networks.html) by default. ### API Servers -All P2P Mode servers provide [APIs](rippled-api.html) for purposes like submitting transactions, checking balances and settings, and administering the server. If you query the XRP Ledger for data or submit transactions for business use, it can be useful to [run your own server](the-rippled-server.html#reasons-to-run-your-own-server). +All P2P Mode servers provide [APIs](rippled-api.html) for purposes like submitting transactions, checking balances and settings, and administering the server. If you query the XRP Ledger for data or submit transactions for business use, it can be useful to [run your own server](xrpl-servers.html#reasons-to-run-your-own-server). #### Full History Servers diff --git a/content/concepts/nodes-and-clients/the-clio-server.md b/content/concepts/xrpl-servers/the-clio-server.md similarity index 91% rename from content/concepts/nodes-and-clients/the-clio-server.md rename to content/concepts/xrpl-servers/the-clio-server.md index 9811910b6c..78bb32b00f 100644 --- a/content/concepts/nodes-and-clients/the-clio-server.md +++ b/content/concepts/xrpl-servers/the-clio-server.md @@ -1,12 +1,11 @@ --- html: the-clio-server.html -parent: concepts.html -template: pagetype-category.html.jinja -blurb: Clio is an XRP Ledger API server optimized for WebSocket or HTTP API calls. +parent: xrpl-servers.html +blurb: Clio is an XRP Ledger server optimized for API calls. --- # The Clio Server -Clio is an XRP Ledger API server optimized for WebSocket or HTTP API calls for validated ledger data. +Clio is an XRP Ledger API server optimized for WebSocket or HTTP API calls for validated ledger data. A Clio server does not connect to the peer-to-peer network. Instead, it extracts data from a specified `rippled` server which is connected to the P2P network. By handling API calls efficiently, Clio servers can help reduce the load on `rippled` servers running in P2P mode. @@ -22,18 +21,18 @@ There are lots of reasons you might want to run your own Clio server, but most o * Reduced load on `rippled` server(s) - A Clio server does not connect to the peer-to-peer network. It uses gRPC to get validated data from one or more trusted `rippled` servers that are connected to the P2P network. Thus, a Clio server handles requests more efficiently and reduces the load on `rippled` servers running in P2P mode. -* Lower memory usage and storage overhead - Clio uses Cassandra as the backend database and stores data in a space efficient format, using up to 4 times less space than `rippled`. +* Lower memory usage and storage overhead - Clio uses Cassandra as the backend database and stores data in a space efficient format, using up to 4 times less space than `rippled`. -* Easier horizontal scaling - Multiple Clio servers can share access to the same dataset, thus enabling you to build a highly available cluster of Clio servers. +* Easier horizontal scaling - Multiple Clio servers can share access to the same dataset, thus enabling you to build a highly available cluster of Clio servers. -* Higher throughput for API requests - A Clio server extracts validated data from one or more trusted `rippled` servers and stores this data efficiently. Thus, handling API calls efficiently, resulting in a higher throughput and in some cases, lower latency as well. +* Higher throughput for API requests - A Clio server extracts validated data from one or more trusted `rippled` servers and stores this data efficiently. Thus, handling API calls efficiently, resulting in a higher throughput and in some cases, lower latency as well. ## How does a Clio Server Work? {{ include_svg("img/clio-basic-architecture.svg", "Figure 1: How does a Clio server work?") }} -A Clio server stores validated ledger data such as transaction metadata, account states, and ledger headers in a persistent datastore. +A Clio server stores validated ledger data such as transaction metadata, account states, and ledger headers in a persistent datastore. When a Clio server receives an API request, it looks up data from these data stores. For requests that require data from the P2P network, the Clio server forwards the request to a P2P server, and then passes the response back to the client. @@ -41,4 +40,4 @@ When a Clio server receives an API request, it looks up data from these data sto ## See Also - **Tutorials:** - - [Install Clio server on Ubuntu](install-clio-on-ubuntu.html) \ No newline at end of file + - [Install Clio server on Ubuntu](install-clio-on-ubuntu.html) diff --git a/content/concepts/the-rippled-server/transaction-censorship-detection.ja.md b/content/concepts/xrpl-servers/transaction-censorship-detection.ja.md similarity index 99% rename from content/concepts/the-rippled-server/transaction-censorship-detection.ja.md rename to content/concepts/xrpl-servers/transaction-censorship-detection.ja.md index 0ca6600092..dafe198ec1 100644 --- a/content/concepts/the-rippled-server/transaction-censorship-detection.ja.md +++ b/content/concepts/xrpl-servers/transaction-censorship-detection.ja.md @@ -1,6 +1,6 @@ --- html: transaction-censorship-detection.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: XRP Ledgerでは取引検閲の自動検知機能がすべてのrippledサーバーで有効になっています。 labels: - ブロックチェーン diff --git a/content/concepts/the-rippled-server/transaction-censorship-detection.md b/content/concepts/xrpl-servers/transaction-censorship-detection.md similarity index 99% rename from content/concepts/the-rippled-server/transaction-censorship-detection.md rename to content/concepts/xrpl-servers/transaction-censorship-detection.md index ab53c79042..37db439584 100644 --- a/content/concepts/the-rippled-server/transaction-censorship-detection.md +++ b/content/concepts/xrpl-servers/transaction-censorship-detection.md @@ -1,6 +1,6 @@ --- html: transaction-censorship-detection.html -parent: the-rippled-server.html +parent: xrpl-servers.html blurb: XRP Ledger provides an automated transaction censorship detector that is available on all rippled servers. labels: - Blockchain diff --git a/content/concepts/the-rippled-server/the-rippled-server.md b/content/concepts/xrpl-servers/xrpl-servers.md similarity index 58% rename from content/concepts/the-rippled-server/the-rippled-server.md rename to content/concepts/xrpl-servers/xrpl-servers.md index bdc9831329..02ce25b757 100644 --- a/content/concepts/the-rippled-server/the-rippled-server.md +++ b/content/concepts/xrpl-servers/xrpl-servers.md @@ -1,33 +1,35 @@ --- -html: the-rippled-server.html +html: xrpl-servers.html parent: concepts.html -template: pagetype-category.html.jinja blurb: rippled is the core peer-to-peer server that manages the XRP Ledger. -labels: - - Core Server -top_nav_name: About the Server +template: pagetype-category.html.jinja --- -# The `rippled` Server +# XRP Ledger Servers -`rippled` is the core peer-to-peer server that manages the XRP Ledger. This section covers concepts that help you learn the "what" and "why" behind fundamental aspects of the `rippled` server. +There are two main types of server software that power the XRP Ledger: + +- The core server, `rippled`, runs the the peer-to-peer network which processes transactions and reaches a consensus on their outcome. +- The API server, [Clio](the-clio-server.html), provides a powerful interface for fetching or querying data from the ledger. + +Anyone can run instances of one or both of these types of servers based on their needs. ## Reasons to Run Your Own Server For lighter use cases and individual servers, you can often rely on free [public servers][]. However, the more serious your use of the XRP Ledger becomes, the more important it becomes to have your own infrastructure. -There are lots of reasons you might want to run your own `rippled` server, but most of them can be summarized as: you can trust your own server, you have control over its workload, and you're not at the mercy of others to decide when and how you can access it. Of course, you must practice good network security to protect your server from malicious hackers. +There are lots of reasons you might want to run your own servers, but most of them can be summarized as: you can trust your own server, you have control over its workload, and you're not at the mercy of others to decide when and how you can access it. Of course, you must practice good network security to protect your server from malicious hackers. -You need to trust the `rippled` you use. If you connect to a malicious server, there are many ways that it can take advantage of you or cause you to lose money. For example: +You need to trust the server you use. If you connect to a malicious server, there are many ways that it can take advantage of you or cause you to lose money. For example: * A malicious server could report that you were paid when no such payment was made. * It could selectively show or hide payment paths and currency exchange offers to guarantee its own profit while not providing you the best deal. * If you sent it your address's secret key, it could make arbitrary transactions on your behalf, and even transfer or destroy all the money your address holds. -Additionally, running your own server gives you [admin access](get-started-using-http-websocket-apis.html#admin-access), which allows you to run important admin-only and load-intensive commands. If you use a shared server, you have to worry about other users of the same server competing with you for the server's computing power. Many of the commands in the WebSocket API can put a lot of strain on the server, so `rippled` has the option to scale back its responses when it needs to. If you share a server with others, you may not always get the best results possible. +Additionally, running your own server gives you [admin access](get-started-using-http-websocket-apis.html#admin-access), which allows you to run important admin-only and load-intensive commands. If you use a shared server, you have to worry about other users of the same server competing with you for the server's computing power. Many of the commands in the WebSocket API can put a lot of strain on the server, so the server has the option to scale back its responses when it needs to. If you share a server with others, you may not always get the best results possible. Finally, if you run a validating server, you can use a stock server as a proxy to the public network while keeping your validating server on a private network only accessible to the outside world through the stock server. This makes it more difficult to compromise the integrity of your validating server. -## rippled Server Features +## Server Features and Topics diff --git a/content/faq.md b/content/faq.md index 433a16035f..3999e5f2b6 100644 --- a/content/faq.md +++ b/content/faq.md @@ -155,4 +155,4 @@ Ripple is also one of several entities who publish recommended UNL settings and #### Does the XRP Ledger distinguish between the codebase for validation and the one for user software? -Yes. There are several [XRP Ledger client libraries](client-libraries.html) which are intended for user software developers. These libraries have different codebases and repositories from the [core XRP Ledger server](the-rippled-server.html) which powers the network and validates transactions. +Yes. There are several [XRP Ledger client libraries](client-libraries.html) which are intended for user software developers. These libraries have different codebases and repositories from the [core XRP Ledger server](xrpl-servers.html) which powers the network and validates transactions. diff --git a/content/references/rippled-api/api-conventions/api-conventions.md b/content/references/rippled-api/api-conventions/api-conventions.md index 73f233eb5f..f7bccf69ba 100644 --- a/content/references/rippled-api/api-conventions/api-conventions.md +++ b/content/references/rippled-api/api-conventions/api-conventions.md @@ -6,6 +6,6 @@ template: pagetype-category.html.jinja --- # API Conventions -This section describes data types and formats of the HTTP APIs (JSON-RPC and WebSocket) as implemented in [the `rippled` server](the-rippled-server.html). +This section describes data types and formats of the HTTP APIs (JSON-RPC and WebSocket) as implemented in [the `rippled` server](xrpl-servers.html). For information on the XRP Ledger protocol that applies to all APIs, see [Protocol Reference](protocol-reference.html). diff --git a/content/references/rippled-api/api-conventions/rate-limiting.md b/content/references/rippled-api/api-conventions/rate-limiting.md index e649bc1751..2584e7e7c3 100644 --- a/content/references/rippled-api/api-conventions/rate-limiting.md +++ b/content/references/rippled-api/api-conventions/rate-limiting.md @@ -54,7 +54,7 @@ The usage rate drops off exponentially over time, so a client that does not make ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Software Ecosystem](software-ecosystem.html) - **Tutorials:** - [Getting Started with XRP Ledger APIs](get-started-using-http-websocket-apis.html) diff --git a/content/references/rippled-api/api-conventions/response-formatting.md b/content/references/rippled-api/api-conventions/response-formatting.md index edc420f996..700b87f6a1 100644 --- a/content/references/rippled-api/api-conventions/response-formatting.md +++ b/content/references/rippled-api/api-conventions/response-formatting.md @@ -183,7 +183,7 @@ It is generally safe to ignore this warning. - [Request Formatting](request-formatting.html) - [Error Formatting](error-formatting.html) for unsuccessful API responses. - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - [Amendments](amendments.html) - [Known Amendments](known-amendments.html) diff --git a/content/tutorials/build-apps/build-a-desktop-wallet-in-python.md b/content/tutorials/build-apps/build-a-desktop-wallet-in-python.md index 024c9fba6c..3519beee3f 100644 --- a/content/tutorials/build-apps/build-a-desktop-wallet-in-python.md +++ b/content/tutorials/build-apps/build-a-desktop-wallet-in-python.md @@ -148,7 +148,7 @@ Finally, change the code to start the app (at the end of the file) slightly: Since the app uses a WebSocket client instead of the JSON-RPC client now, the code has to be use WebSocket URL to connect. -**Tip:** If you [run your own `rippled` server](the-rippled-server.html#reasons-to-run-your-own-server) you can connect to it using `ws://localhost:6006` as the URL. You can also use the WebSocket URLs of [public servers](public-servers.html) to connect to the Mainnet or other test networks. +**Tip:** If you [run your own `rippled` server](xrpl-servers.html#reasons-to-run-your-own-server) you can connect to it using `ws://localhost:6006` as the URL. You can also use the WebSocket URLs of [public servers](public-servers.html) to connect to the Mainnet or other test networks. #### Troubleshooting SSL Certificate Errors diff --git a/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md b/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md index 173e3e4cea..df205883c0 100644 --- a/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md +++ b/content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md @@ -11,7 +11,7 @@ showcase_icon: assets/img/logos/globe.svg --- # HTTP / WebSocket APIの使用開始 -XRP Ledgerのコアサーバーソフトウェアは[`rippled`](the-rippled-server.html)です。XRP Ledgerでの開発に進むには、`rippled`サーバーのAPIにアクセスします。 +XRP Ledgerのコアサーバーソフトウェアは[`rippled`](xrpl-servers.html)です。XRP Ledgerでの開発に進むには、`rippled`サーバーのAPIにアクセスします。 APIにアクセスする最も簡単な方法は、[**WebSocket API Tool**](websocket-api-tool.html)を使用するか、[XRP Ledger Explorer](https://livenet.xrpl.org/)を使用してレジャーの進行状況をその場で確認することです。 diff --git a/content/tutorials/get-started/get-started-using-http-websocket-apis.md b/content/tutorials/get-started/get-started-using-http-websocket-apis.md index 5b8c851d81..08c3ae80a0 100644 --- a/content/tutorials/get-started/get-started-using-http-websocket-apis.md +++ b/content/tutorials/get-started/get-started-using-http-websocket-apis.md @@ -11,7 +11,7 @@ showcase_icon: assets/img/logos/globe.svg --- # Get Started Using HTTP / WebSocket APIs -If you don't have or don't want to use a [client library](client-libraries.html) in your preferred programming language, you can access the XRP Ledger directly through the APIs of its core server software, [`rippled`](the-rippled-server.html). The server provides APIs over JSON-RPC and WebSocket protocols. If you don't [run your own instance of `rippled`](install-rippled.html) you can still use a [public server][public servers]. +If you don't have or don't want to use a [client library](client-libraries.html) in your preferred programming language, you can access the XRP Ledger directly through the APIs of its core server software, [`rippled`](xrpl-servers.html). The server provides APIs over JSON-RPC and WebSocket protocols. If you don't [run your own instance of `rippled`](install-rippled.html) you can still use a [public server][public servers]. **Tip:** You can dive right into the API with the [**WebSocket API Tool**](websocket-api-tool.html), or use the [XRP Ledger Explorer](https://livenet.xrpl.org/) to watch the progress of the ledger live. diff --git a/content/tutorials/get-started/get-started-using-java.md b/content/tutorials/get-started/get-started-using-java.md index ef5906b4b1..1b1670b902 100644 --- a/content/tutorials/get-started/get-started-using-java.md +++ b/content/tutorials/get-started/get-started-using-java.md @@ -96,7 +96,7 @@ you can use an [`XrplClient`](https://javadoc.io/doc/org.xrpl/xrpl4j-client/late The sample code in the previous section shows you how to connect to the Testnet, which is one of the available [parallel networks](parallel-networks.html). When you're ready to integrate with the production XRP Ledger, you'll need to connect to the Mainnet. You can do that in two ways: -* By [installing the core server](install-rippled.html) (`rippled`) and running a node yourself. The core server connects to the Mainnet by default, but you can [change the configuration to use Testnet or Devnet](connect-your-rippled-to-the-xrp-test-net.html). [There are good reasons to run your own core server](the-rippled-server.html#reasons-to-run-your-own-server). If you run your own server, you can connect to it like so: +* By [installing the core server](install-rippled.html) (`rippled`) and running a node yourself. The core server connects to the Mainnet by default, but you can [change the configuration to use Testnet or Devnet](connect-your-rippled-to-the-xrp-test-net.html). [There are good reasons to run your own core server](xrpl-servers.html#reasons-to-run-your-own-server). If you run your own server, you can connect to it like so: final HttpUrl rippledUrl = HttpUrl.get("http://localhost:5005/"); XrplClient xrplClient = new XrplClient(rippledUrl); diff --git a/content/tutorials/get-started/get-started-using-javascript.ja.md b/content/tutorials/get-started/get-started-using-javascript.ja.md index 011de6edd7..bea9db847a 100644 --- a/content/tutorials/get-started/get-started-using-javascript.ja.md +++ b/content/tutorials/get-started/get-started-using-javascript.ja.md @@ -97,7 +97,7 @@ const xrpl = require("xrpl") 前節のサンプルコードでは、利用可能な[並列ネットワーク](parallel-networks.html)の1つであるTestnetに接続する方法を紹介しました。本番環境に移行するには、XRP Ledger Mainnetに接続する必要があります。それには2つの方法があります。 -* [コアサーバをインストール](install-rippled.html) (`rippled`)して、自分でノードを動かしてみましょう。コアサーバーはデフォルトではMainnetに接続しますが、設定を変更してTestnetやDevnetを使うこともできます](connect-your-rippled-to-thexrp-test-net.html)。[独自のコアサーバーを運用するのには良い理由があります](the-rippled-server.html#reasons-to-run-your-own-server)。独自のサーバーを走らせた場合、次のようにして接続することができます。 +* [コアサーバをインストール](install-rippled.html) (`rippled`)して、自分でノードを動かしてみましょう。コアサーバーはデフォルトではMainnetに接続しますが、設定を変更してTestnetやDevnetを使うこともできます](connect-your-rippled-to-thexrp-test-net.html)。[独自のコアサーバーを運用するのには良い理由があります](xrpl-servers.html#reasons-to-run-your-own-server)。独自のサーバーを走らせた場合、次のようにして接続することができます。 const MY_SERVER = "ws://localhost:6006/" const client = new xrpl.Client(MY_SERVER) diff --git a/content/tutorials/get-started/get-started-using-javascript.md b/content/tutorials/get-started/get-started-using-javascript.md index f25400e8bf..f339e834b4 100644 --- a/content/tutorials/get-started/get-started-using-javascript.md +++ b/content/tutorials/get-started/get-started-using-javascript.md @@ -97,7 +97,7 @@ To make queries and submit transactions, you need to establish a connection to t The sample code in the previous section shows you how to connect to the Testnet, which is one of the available [parallel networks](parallel-networks.html). When you're ready to move to production, you'll need to connect to the XRP Ledger Mainnet. You can do that in two ways: -* By [installing the core server](install-rippled.html) (`rippled`) and running a node yourself. The core server connects to the Mainnet by default, but you can [change the configuration to use Testnet or Devnet](connect-your-rippled-to-the-xrp-test-net.html). [There are good reasons to run your own core server](the-rippled-server.html#reasons-to-run-your-own-server). If you run your own server, you can connect to it like so: +* By [installing the core server](install-rippled.html) (`rippled`) and running a node yourself. The core server connects to the Mainnet by default, but you can [change the configuration to use Testnet or Devnet](connect-your-rippled-to-the-xrp-test-net.html). [There are good reasons to run your own core server](xrpl-servers.html#reasons-to-run-your-own-server). If you run your own server, you can connect to it like so: const MY_SERVER = "ws://localhost:6006/" const client = new xrpl.Client(MY_SERVER) diff --git a/content/tutorials/get-started/get-started-using-python.md b/content/tutorials/get-started/get-started-using-python.md index fcefc58c82..f64710445c 100644 --- a/content/tutorials/get-started/get-started-using-python.md +++ b/content/tutorials/get-started/get-started-using-python.md @@ -65,7 +65,7 @@ To make queries and submit transactions, you need to establish a connection to t The sample code in the previous section shows you how to connect to the Testnet, which is one of the available [parallel networks](parallel-networks.html). When you're ready to integrate with the production XRP Ledger, you'll need to connect to the Mainnet. You can do that in two ways: -* By [installing the core server](install-rippled.html) (`rippled`) and running a node yourself. The core server connects to the Mainnet by default, but you can [change the configuration to use Testnet or Devnet](connect-your-rippled-to-the-xrp-test-net.html). [There are good reasons to run your own core server](the-rippled-server.html#reasons-to-run-your-own-server). If you run your own server, you can connect to it like so: +* By [installing the core server](install-rippled.html) (`rippled`) and running a node yourself. The core server connects to the Mainnet by default, but you can [change the configuration to use Testnet or Devnet](connect-your-rippled-to-the-xrp-test-net.html). [There are good reasons to run your own core server](xrpl-servers.html#reasons-to-run-your-own-server). If you run your own server, you can connect to it like so: from xrpl.clients import JsonRpcClient JSON_RPC_URL = "http://localhost:5005/" diff --git a/content/tutorials/get-started/send-xrp.md b/content/tutorials/get-started/send-xrp.md index e64ce706e4..8f1151b169 100644 --- a/content/tutorials/get-started/send-xrp.md +++ b/content/tutorials/get-started/send-xrp.md @@ -377,7 +377,7 @@ XrplClient xrplClient = new XrplClient(rippledUrl); -If you [install `rippled`](install-rippled.html) yourself, it connects to the production network by default. (You can also [configure it to connect to the test net](connect-your-rippled-to-the-xrp-test-net.html) instead.) After the server has synced (typically within about 15 minutes of starting it up), you can connect to it locally, which has [various benefits](the-rippled-server.html). The following example shows how to connect to a server running the default configuration: +If you [install `rippled`](install-rippled.html) yourself, it connects to the production network by default. (You can also [configure it to connect to the test net](connect-your-rippled-to-the-xrp-test-net.html) instead.) After the server has synced (typically within about 15 minutes of starting it up), you can connect to it locally, which has [various benefits](xrpl-servers.html). The following example shows how to connect to a server running the default configuration: diff --git a/content/tutorials/manage-the-clio-server/build-run-clio-ubuntu.md b/content/tutorials/manage-the-clio-server/build-run-clio-ubuntu.md index de42476bca..1510a488bd 100644 --- a/content/tutorials/manage-the-clio-server/build-run-clio-ubuntu.md +++ b/content/tutorials/manage-the-clio-server/build-run-clio-ubuntu.md @@ -5,7 +5,7 @@ blurb: Compile Clio yourself on Ubuntu Linux. --- # Build and Run Clio on Ubuntu -[`rippled`](the-rippled-server.html) is the reference implementation of an XRP Ledger peer-to-peer server. This server can connect to a network of peers, relay cryptographically signed transactions, and maintain a local copy of the complete shared global ledger. Use these instructions to build a `rippled` executable from source. These instructions were tested on Ubuntu 18.04 LTS. +[`rippled`](xrpl-servers.html) is the reference implementation of an XRP Ledger peer-to-peer server. This server can connect to a network of peers, relay cryptographically signed transactions, and maintain a local copy of the complete shared global ledger. Use these instructions to build a `rippled` executable from source. These instructions were tested on Ubuntu 18.04 LTS. ## Prerequisites @@ -208,7 +208,7 @@ Watchdog: Launching child 1 ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Configure rippled](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/configuration/configure-advisory-deletion.md b/content/tutorials/manage-the-rippled-server/configuration/configure-advisory-deletion.md index 49427d6cff..577820f274 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/configure-advisory-deletion.md +++ b/content/tutorials/manage-the-rippled-server/configuration/configure-advisory-deletion.md @@ -8,7 +8,7 @@ labels: --- # Configure Advisory Deletion -The default config file sets [`rippled`](the-rippled-server.html) to automatically delete outdated [history](ledger-history.html) of XRP Ledger state and transactions as new ledger versions become available. If your server uses most of its hardware resources during peak hours, you can configure the server to delete ledgers only when prompted by a command scheduled to run during off-peak hours, so that online deletion is less likely to impact [server performance](capacity-planning.html). +The default config file sets [`rippled`](xrpl-servers.html) to automatically delete outdated [history](ledger-history.html) of XRP Ledger state and transactions as new ledger versions become available. If your server uses most of its hardware resources during peak hours, you can configure the server to delete ledgers only when prompted by a command scheduled to run during off-peak hours, so that online deletion is less likely to impact [server performance](capacity-planning.html). ## Prerequisites diff --git a/content/tutorials/manage-the-rippled-server/configuration/configure-online-deletion.md b/content/tutorials/manage-the-rippled-server/configuration/configure-online-deletion.md index 97085aed05..8d5a923c5a 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/configure-online-deletion.md +++ b/content/tutorials/manage-the-rippled-server/configuration/configure-online-deletion.md @@ -8,7 +8,7 @@ labels: --- # Configure Online Deletion -In its default configuration, [the `rippled` server](the-rippled-server.html) [deletes history](online-deletion.html) older than the most recent 2000 [ledger versions](ledgers.html), keeping approximately 15 minutes of [ledger history](ledger-history.html) (based on the current rate between ledgers). This page describes how to configure the amount of history your `rippled` server stores before deleting. +In its default configuration, [the `rippled` server](xrpl-servers.html) [deletes history](online-deletion.html) older than the most recent 2000 [ledger versions](ledgers.html), keeping approximately 15 minutes of [ledger history](ledger-history.html) (based on the current rate between ledgers). This page describes how to configure the amount of history your `rippled` server stores before deleting. ## Prerequisites diff --git a/content/tutorials/manage-the-rippled-server/configuration/configure-statsd.md b/content/tutorials/manage-the-rippled-server/configuration/configure-statsd.md index 24d7263660..3c91ae3547 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/configure-statsd.md +++ b/content/tutorials/manage-the-rippled-server/configuration/configure-statsd.md @@ -58,7 +58,7 @@ For descriptions of each StatsD metric, see the [`rippledmon` repository](https: - **Concepts:** - [XRP Ledger Overview](xrp-ledger-overview.html) - [Consensus Network](consensus-network.html) - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - **Tutorials:** - [Install `rippled`](install-rippled.html) - [Capacity Planning](capacity-planning.html) diff --git a/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.ja.md b/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.ja.md index 105433125a..026ded7f4b 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.ja.md +++ b/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.ja.md @@ -9,7 +9,7 @@ labels: --- # XRPL Altnetへのrippledの接続 -Rippleは[代替となるテスト用および開発用ネットワーク](parallel-networks.html)を作成しており、開発者が最新のXRP Ledgerの非本番バージョン（Testnet）でアプリケーションをテストしたり、最新のベータバージョン（Devnet）で機能をテストして実験したりできるようにしています。 **これらのネットワークで使用する資金は実際の資金ではなく、テスト専用の資金です。** TestnetまたはDevnetの[`rippled`サーバー](the-rippled-server.html)に接続できます。 +Rippleは[代替となるテスト用および開発用ネットワーク](parallel-networks.html)を作成しており、開発者が最新のXRP Ledgerの非本番バージョン（Testnet）でアプリケーションをテストしたり、最新のベータバージョン（Devnet）で機能をテストして実験したりできるようにしています。 **これらのネットワークで使用する資金は実際の資金ではなく、テスト専用の資金です。** TestnetまたはDevnetの[`rippled`サーバー](xrpl-servers.html)に接続できます。 **注記:** XRP TestnetとDevnetのレジャーと残高は定期的にリセットされます。 diff --git a/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md b/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md index 4a9973d860..5c64454d60 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md +++ b/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md @@ -9,7 +9,7 @@ labels: --- # Connect Your rippled to a Parallel Network -Various [alternative test and development networks](parallel-networks.html) exist for developers to test their apps or experiment with features without risking real money. **The funds used on these networks are not real funds and are intended for testing only.** You can connect your [`rippled` server](the-rippled-server.html) to any of these test networks. +Various [alternative test and development networks](parallel-networks.html) exist for developers to test their apps or experiment with features without risking real money. **The funds used on these networks are not real funds and are intended for testing only.** You can connect your [`rippled` server](xrpl-servers.html) to any of these test networks. **Caution:** On test networks with new and experimental features, you may need to run a pre-production release of the server to sync with the network. See the [Parallel Networks Page](parallel-networks.html) for information on what code version each network needs. diff --git a/content/tutorials/manage-the-rippled-server/configuration/enable-public-signing.md b/content/tutorials/manage-the-rippled-server/configuration/enable-public-signing.md index 1bf9211d64..8c95cb916b 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/enable-public-signing.md +++ b/content/tutorials/manage-the-rippled-server/configuration/enable-public-signing.md @@ -8,7 +8,7 @@ labels: --- # Enable Public Signing -By default, the signing methods for [`rippled`](the-rippled-server.html) are limited to [administrative connections](admin-rippled-methods.html). If you want to allow signing methods to be used as public API methods (like with versions of `rippled` before v1.1.0), you can enable it with a configuration change. [New in: rippled 1.1.0][] +By default, the signing methods for [`rippled`](xrpl-servers.html) are limited to [administrative connections](admin-rippled-methods.html). If you want to allow signing methods to be used as public API methods (like with versions of `rippled` before v1.1.0), you can enable it with a configuration change. [New in: rippled 1.1.0][] This enables the following methods to be used on "public" [JSON-RPC and WebSocket connections](get-started-using-http-websocket-apis.html), if your server accepts them: diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.ja.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.ja.md index c93ac26e6d..3bad8adc58 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.ja.md +++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.ja.md @@ -10,7 +10,7 @@ top_nav_name: UNLに参加しよう --- # バリデータとしてのrippledの実行 -[バリデータモード](rippled-server-modes.html)で実行されている[`rippled`サーバー](the-rippled-server.html)は、ストックサーバーが実行するあらゆる処理を実行します。 +[バリデータモード](rippled-server-modes.html)で実行されている[`rippled`サーバー](xrpl-servers.html)は、ストックサーバーが実行するあらゆる処理を実行します。 - [ピアのネットワーク](consensus-network.html)への接続 @@ -294,7 +294,7 @@ _**公開ハブを使用してバリデータをネットワークに接続す - **コンセプト:** - [XRP Ledgerの概要](xrp-ledger-overview.html) - [コンセンサスネットワーク](consensus-network.html) - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - **チュートリアル:** - [rippledサーバーのクラスター化](cluster-rippled-servers.html) - [`rippled`のインストール](install-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md index 3a9eabe358..73ae4e25d2 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md +++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md @@ -10,7 +10,7 @@ top_nav_name: Join UNL --- # Run rippled as a Validator -A [`rippled` server](the-rippled-server.html) running in [validator mode](rippled-server-modes.html) does everything a stock server does: +A [`rippled` server](xrpl-servers.html) running in [validator mode](rippled-server-modes.html) does everything a stock server does: - Connects to a [network of peers](consensus-network.html) @@ -264,7 +264,7 @@ For information about how to revoke a master key pair you generated for your val - **Concepts:** - [XRP Ledger Overview](xrp-ledger-overview.html) - [Consensus Network](consensus-network.html) - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - **Tutorials:** - [Cluster rippled Servers](cluster-rippled-servers.html) - [Install `rippled`](install-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.ja.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.ja.md index 8ccb7486b3..9c56bbc940 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.ja.md +++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.ja.md @@ -45,7 +45,7 @@ labels: - **コンセプト:** - [XRP Ledgerの概要](xrp-ledger-overview.html) - [コンセンサスネットワーク](consensus-network.html) - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - **チュートリアル:** - [rippledサーバーのクラスター化](cluster-rippled-servers.html) - [`rippled`のインストール](install-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md index a27f438c82..ea3e3f6485 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md +++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-wallet-server.md @@ -45,7 +45,7 @@ For more information, see [Troubleshooting `rippled`](troubleshoot-the-rippled-s - **Concepts:** - [XRP Ledger Overview](xrp-ledger-overview.html) - [Consensus Network](consensus-network.html) - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - **Tutorials:** - [Cluster rippled Servers](cluster-rippled-servers.html) - [Install `rippled`](install-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/configure-peering/cluster-rippled-servers.md b/content/tutorials/manage-the-rippled-server/configure-peering/cluster-rippled-servers.md index d9372dd559..d8e6d34b37 100644 --- a/content/tutorials/manage-the-rippled-server/configure-peering/cluster-rippled-servers.md +++ b/content/tutorials/manage-the-rippled-server/configure-peering/cluster-rippled-servers.md @@ -7,7 +7,7 @@ labels: --- # Cluster rippled Servers -If you run multiple [`rippled` servers](the-rippled-server.html) in the same data center, you can configure them in a [cluster](clustering.html) to maximize efficiency. To configure clustering: +If you run multiple [`rippled` servers](xrpl-servers.html) in the same data center, you can configure them in a [cluster](clustering.html) to maximize efficiency. To configure clustering: 1. For each of your servers, note the IP address of the server. diff --git a/content/tutorials/manage-the-rippled-server/configure-peering/configure-the-peer-crawler.md b/content/tutorials/manage-the-rippled-server/configure-peering/configure-the-peer-crawler.md index 6a4cfeb403..00266adaf1 100644 --- a/content/tutorials/manage-the-rippled-server/configure-peering/configure-the-peer-crawler.md +++ b/content/tutorials/manage-the-rippled-server/configure-peering/configure-the-peer-crawler.md @@ -8,7 +8,7 @@ labels: --- # Configure the Peer Crawler -By default, [`rippled` servers](the-rippled-server.html) provide statistics publicly to anyone who asks using the [peer crawler API](peer-crawler.html), to make it easier to track the health and topology of [the XRP Ledger's peer-to-peer network](consensus-network.html). You can configure your server to provide more or less information, or to reject peer crawler requests entirely. [New in: rippled 1.2.0][] +By default, [`rippled` servers](xrpl-servers.html) provide statistics publicly to anyone who asks using the [peer crawler API](peer-crawler.html), to make it easier to track the health and topology of [the XRP Ledger's peer-to-peer network](consensus-network.html). You can configure your server to provide more or less information, or to reject peer crawler requests entirely. [New in: rippled 1.2.0][] This document contains steps for two options: diff --git a/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.ja.md b/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.ja.md index eb07b5d780..5a0e4c65ba 100644 --- a/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.ja.md +++ b/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.ja.md @@ -50,7 +50,7 @@ $ sudo firewall-cmd --add-forward-port=port=51235:proto=tcp:toport=51235 - **コンセプト:** - [ピアプロトコル](peer-protocol.html) - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - **チュートリアル:** - [容量の計画](capacity-planning.html) - [`rippled`サーバーのトラブルシューティング](troubleshoot-the-rippled-server.html) diff --git a/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md b/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md index 50a1fe38ef..27e8b7c3c1 100644 --- a/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md +++ b/content/tutorials/manage-the-rippled-server/configure-peering/forward-ports-for-peering.md @@ -68,7 +68,7 @@ If you are using a hosting service with a virtual firewall (for example, [AWS Se - **Concepts:** - [Peer Protocol](peer-protocol.html) - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - **Tutorials:** - [Capacity Planning](capacity-planning.html) - [Troubleshoot the `rippled` Server](troubleshoot-the-rippled-server.html) diff --git a/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.ja.md b/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.ja.md index b4c966b381..c917419337 100644 --- a/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.ja.md +++ b/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.ja.md @@ -63,7 +63,7 @@ rippled connect 169.54.2.151 51235 - **コンセプト:** - [ピアプロトコル](peer-protocol.html) - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - **チュートリアル:** - [容量の計画](capacity-planning.html) - [`rippled`サーバーのトラブルシューティング](troubleshoot-the-rippled-server.html) diff --git a/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.md b/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.md index b5a509c388..fad1577ec5 100644 --- a/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.md +++ b/content/tutorials/manage-the-rippled-server/configure-peering/manually-connect-to-a-specific-peer.md @@ -63,7 +63,7 @@ rippled connect 169.54.2.151 51235 - **Concepts:** - [Peer Protocol](peer-protocol.html) - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - **Tutorials:** - [Capacity Planning](capacity-planning.html) - [Troubleshoot the `rippled` Server](troubleshoot-the-rippled-server.html) diff --git a/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.ja.md b/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.ja.md index f8677ee3ad..992e8df433 100644 --- a/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.ja.md +++ b/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.ja.md @@ -39,7 +39,7 @@ labels: - **コンセプト:** - [ピアプロトコル](peer-protocol.html) - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - **チュートリアル:** - [容量の計画](capacity-planning.html) - [`rippled`サーバーのトラブルシューティング](troubleshoot-the-rippled-server.html) diff --git a/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.md b/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.md index f6cfa3a9e2..dcab3ee367 100644 --- a/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.md +++ b/content/tutorials/manage-the-rippled-server/configure-peering/set-max-number-of-peers.md @@ -39,7 +39,7 @@ To change the maximum number of peers your server allows, complete the following - **Concepts:** - [Peer Protocol](peer-protocol.html) - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - **Tutorials:** - [Capacity Planning](capacity-planning.html) - [Troubleshoot the `rippled` Server](troubleshoot-the-rippled-server.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md index 621a585914..e2435fed0a 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.ja.md @@ -7,7 +7,7 @@ labels: --- # macOSでのrippledの構築と実行 -[`rippled`](the-rippled-server.html)の本番環境にmacOSプラットフォームを使用することは推奨されていません。本番環境には、最高レベルの品質管理とテストを経た、[Ubuntuプラットフォーム](install-rippled-on-ubuntu-with-alien.html)のご使用をご検討ください。 +[`rippled`](xrpl-servers.html)の本番環境にmacOSプラットフォームを使用することは推奨されていません。本番環境には、最高レベルの品質管理とテストを経た、[Ubuntuプラットフォーム](install-rippled-on-ubuntu-with-alien.html)のご使用をご検討ください。 しかしながら、macOSは多くの開発やテストの作業に適しています。`rippled`は、10.15.7 CatalinaまでのmacOSでテスト済みです。 @@ -177,7 +177,7 @@ labels: ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [Ubuntu Linuxでrippledをインストール](install-rippled-on-ubuntu.html)（本番環境用の、Ubuntu上の事前構築済みバイナリーをインストール） diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md index 375aa706bd..8743efe1e2 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md @@ -7,7 +7,7 @@ labels: --- # Build and Run rippled on macOS -The macOS platform is not recommended for [`rippled`](the-rippled-server.html) production use. For production, consider using the [Ubuntu platform](install-rippled-on-ubuntu-with-alien.html), which has received the highest level of quality assurance and testing. +The macOS platform is not recommended for [`rippled`](xrpl-servers.html) production use. For production, consider using the [Ubuntu platform](install-rippled-on-ubuntu-with-alien.html), which has received the highest level of quality assurance and testing. That said, macOS is suitable for many development and testing tasks. `rippled` has been tested for use with macOS up to 10.15.7 Catalina. @@ -191,7 +191,7 @@ For information about `rippled` log messages, see [Understanding Log Messages](u ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Install rippled on Ubuntu Linux](install-rippled-on-ubuntu.html) - Install a pre-built binary on Ubuntu for production use diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md index e0e31157be..1d838d937f 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.ja.md @@ -217,7 +217,7 @@ Watchdog: Launching child 1 ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [rippledの構成](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md index 02f3e87095..3f8bbccaf6 100644 --- a/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md +++ b/content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md @@ -7,7 +7,7 @@ labels: --- # Build and Run rippled on Ubuntu -[`rippled`](the-rippled-server.html) is the reference implementation of an XRP Ledger peer-to-peer server. This server can connect to a network of peers, relay cryptographically signed transactions, and maintain a local copy of the complete shared global ledger. Use these instructions to build a `rippled` executable from source. These instructions were tested on Ubuntu 18.04 LTS. +[`rippled`](xrpl-servers.html) is the reference implementation of an XRP Ledger peer-to-peer server. This server can connect to a network of peers, relay cryptographically signed transactions, and maintain a local copy of the complete shared global ledger. Use these instructions to build a `rippled` executable from source. These instructions were tested on Ubuntu 18.04 LTS. For information about building for other platforms, see [Builds](https://github.com/ripple/rippled/tree/develop/Builds) in the `rippled` GitHub repository. @@ -212,7 +212,7 @@ Watchdog: Launching child 1 ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Configure rippled](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/capacity-planning.ja.md b/content/tutorials/manage-the-rippled-server/installation/capacity-planning.ja.md index 686a6993f3..5a9fdd67f8 100644 --- a/content/tutorials/manage-the-rippled-server/installation/capacity-planning.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/capacity-planning.ja.md @@ -199,7 +199,7 @@ AWSインスタンスストア（`ephemeral`ストレージ）では適切なパ ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [`rippled`の構成](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md b/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md index d85a8fd003..96af6ea802 100644 --- a/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md +++ b/content/tutorials/manage-the-rippled-server/installation/capacity-planning.md @@ -197,7 +197,7 @@ You can save bandwidth by [enabling compression on peer-to-peer communications]( ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Configure rippled](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.ja.md b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.ja.md index d1c76350c2..890387294c 100644 --- a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.ja.md @@ -62,7 +62,7 @@ labels: ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [rippledの構成](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.md b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.md index 3126e8c804..aa536971da 100644 --- a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.md +++ b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.md @@ -110,7 +110,7 @@ Before you install `rippled`, you must meet the [System Requirements](system-req ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Configure rippled](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.ja.md b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.ja.md index 4a3938d7be..66d64224af 100644 --- a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.ja.md @@ -96,7 +96,7 @@ labels: ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [rippledの構成](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.md b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.md index fc20e540e4..069891d725 100644 --- a/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.md +++ b/content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.md @@ -104,7 +104,7 @@ Before you install `rippled`, you must meet the [System Requirements](system-req ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Configure rippled](configure-rippled.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.ja.md b/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.ja.md index 68fd58a069..eea2a0e503 100644 --- a/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.ja.md @@ -93,7 +93,7 @@ Rippleの公式RPMリポジトリとそれを使用するための手順が変 - **[`rippled` v1.3.1リリースノート](https://github.com/ripple/rippled/releases/1.3.1)** - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [Linuxでの自動更新](update-rippled-automatically-on-linux.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.md b/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.md index e5650e63a4..df5d12c08d 100644 --- a/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.md +++ b/content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.md @@ -94,7 +94,7 @@ The `rippled` v1.3 package includes an updated auto-update script that works on - **[`rippled` v1.3.1 Release Notes](https://github.com/ripple/rippled/releases/1.3.1)** - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Update Automatically on Linux](update-rippled-automatically-on-linux.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/system-requirements.ja.md b/content/tutorials/manage-the-rippled-server/installation/system-requirements.ja.md index 586b2959db..c189496fe1 100644 --- a/content/tutorials/manage-the-rippled-server/installation/system-requirements.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/system-requirements.ja.md @@ -38,7 +38,7 @@ labels: ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [容量の計画](capacity-planning.html) - 本番環境向けの推奨仕様および計画についての詳細情報 diff --git a/content/tutorials/manage-the-rippled-server/installation/system-requirements.md b/content/tutorials/manage-the-rippled-server/installation/system-requirements.md index d7c232f71a..d10acddf6d 100644 --- a/content/tutorials/manage-the-rippled-server/installation/system-requirements.md +++ b/content/tutorials/manage-the-rippled-server/installation/system-requirements.md @@ -42,7 +42,7 @@ A `rippled` server relies on maintaining accurate time. It is recommended that t ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Capacity Planning](capacity-planning.html) - More information on the recommended specifications and planning for production needs diff --git a/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.ja.md b/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.ja.md index 584d2fe632..4eddfe1144 100644 --- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.ja.md @@ -34,7 +34,7 @@ Linuxでは、`rippled`が1回限りの`cron`構成を使用して最新バー ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [容量の計画](capacity-planning.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.md b/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.md index b2c5115970..19a88e97af 100644 --- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.md +++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-automatically-on-linux.md @@ -32,7 +32,7 @@ To set up automatic updates, complete the following steps: ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [Capacity Planning](capacity-planning.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.ja.md b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.ja.md index e0801e4b5c..872af9f174 100644 --- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.ja.md @@ -44,7 +44,7 @@ labels: ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [`rippled` v1.3.xへの移行手順](rippled-1-3-migration-instructions.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md index a6924d8368..1237dad15b 100644 --- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md +++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-centos-rhel.md @@ -46,7 +46,7 @@ To update manually, complete the following steps: ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [`rippled` v1.3.x Migration Instructions](rippled-1-3-migration-instructions.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.ja.md b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.ja.md index cea48aa3ac..008d803fce 100644 --- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.ja.md +++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.ja.md @@ -36,7 +36,7 @@ labels: ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [コンセンサスについて](intro-to-consensus.html) - **チュートリアル:** - [`rippled` v1.3.xへの移行手順](rippled-1-3-migration-instructions.html) diff --git a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.md b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.md index 84a52170b6..4375125a11 100644 --- a/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.md +++ b/content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.md @@ -41,7 +41,7 @@ To update manually, complete the following steps: ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Introduction to Consensus](intro-to-consensus.html) - **Tutorials:** - [`rippled` v1.3.x Migration Instructions](rippled-1-3-migration-instructions.html) diff --git a/content/tutorials/manage-the-rippled-server/stand-alone-mode/advance-the-ledger-in-stand-alone-mode.md b/content/tutorials/manage-the-rippled-server/stand-alone-mode/advance-the-ledger-in-stand-alone-mode.md index 6a0474e38d..21df940f88 100644 --- a/content/tutorials/manage-the-rippled-server/stand-alone-mode/advance-the-ledger-in-stand-alone-mode.md +++ b/content/tutorials/manage-the-rippled-server/stand-alone-mode/advance-the-ledger-in-stand-alone-mode.md @@ -21,7 +21,7 @@ Whenever `rippled` closes a ledger, it reorders the transactions according to a ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [`rippled` Server Modes](rippled-server-modes.html) - [Introduction to Consensus](intro-to-consensus.html) - [Amendments](amendments.html) diff --git a/content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.ja.md b/content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.ja.md index cf05958069..83cab4ed57 100644 --- a/content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.ja.md +++ b/content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.ja.md @@ -72,7 +72,7 @@ rippled ledger_accept --conf=/path/to/rippled.cfg ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [`rippled`サーバーのモード](rippled-server-modes.html) - [コンセンサスについて](intro-to-consensus.html) - [Amendment](amendments.html) diff --git a/content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.md b/content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.md index 312f9c5f36..25a6a40f0a 100644 --- a/content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.md +++ b/content/tutorials/manage-the-rippled-server/stand-alone-mode/load-a-saved-ledger-in-stand-alone-mode.md @@ -73,7 +73,7 @@ rippled ledger_accept --conf=/path/to/rippled.cfg ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [`rippled` Server Modes](rippled-server-modes.html) - [Introduction to Consensus](intro-to-consensus.html) - [Amendments](amendments.html) diff --git a/content/tutorials/manage-the-rippled-server/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md b/content/tutorials/manage-the-rippled-server/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md index 335f1ef791..d2b757ce79 100644 --- a/content/tutorials/manage-the-rippled-server/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md +++ b/content/tutorials/manage-the-rippled-server/stand-alone-mode/start-a-new-genesis-ledger-in-stand-alone-mode.md @@ -32,7 +32,7 @@ By default, a new genesis ledger has no [amendments](amendments.html) enabled. I ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [`rippled` Server Modes](rippled-server-modes.html) - [Parallel Networks](parallel-networks.html) - [Amendments](amendments.html) diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.ja.md b/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.ja.md index cf3348c708..958f0a5202 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.ja.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.ja.md @@ -119,7 +119,7 @@ rippled server_info ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [Amendment](amendments.html) - **チュートリアル:** - [容量の計画](capacity-planning.html) diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.md b/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.md index 86e1c82b3d..182b2386b9 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.md @@ -162,7 +162,7 @@ To use the script: ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Amendments](amendments.html) - **Tutorials:** - [Capacity Planning](capacity-planning.html) diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/fix-sqlite-tx-db-page-size-issue.md b/content/tutorials/manage-the-rippled-server/troubleshooting/fix-sqlite-tx-db-page-size-issue.md index 318a5e428c..003a6b7afc 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/fix-sqlite-tx-db-page-size-issue.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/fix-sqlite-tx-db-page-size-issue.md @@ -176,7 +176,7 @@ To migrate your transaction database to a larger page size, perform the followin ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Ledger History](ledger-history.html) - **Tutorials:** - [Understanding Log Messages](understanding-log-messages.html) diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.ja.md b/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.ja.md index a0d6125017..77a0864c11 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.ja.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.ja.md @@ -7,7 +7,7 @@ labels: --- # rippledサーバーが同期しない -このページでは、[`rippled`サーバー](the-rippled-server.html)が正常に起動したのに、ネットワークに完全に接続できずに[「connected」状態](rippled-server-states.html)のままになっている場合の原因について説明します。（サーバーが起動中または起動直後にクラッシュした場合は、[サーバーが起動しない](server-wont-start.html)を参照してください。） +このページでは、[`rippled`サーバー](xrpl-servers.html)が正常に起動したのに、ネットワークに完全に接続できずに[「connected」状態](rippled-server-states.html)のままになっている場合の原因について説明します。（サーバーが起動中または起動直後にクラッシュした場合は、[サーバーが起動しない](server-wont-start.html)を参照してください。） 以下の手順では、サポートされているプラットフォームに[`rippled`がインストール](install-rippled.html)されていることを前提としています。 @@ -97,7 +97,7 @@ labels: ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [ピアプロトコル](peer-protocol.html) - [技術に関するよくある質問](technical-faq.html) - **チュートリアル:** diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.md b/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.md index c9bb582618..466a246d65 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/server-doesnt-sync.md @@ -7,7 +7,7 @@ labels: --- # rippled Server Doesn't Sync -This page explains possible reasons [a `rippled` server](the-rippled-server.html) may start successfully, but get stuck in a ["connected" state](rippled-server-states.html) without ever fully connecting to the network. (If the server crashes during or shortly after startup, see [Server Won't Start](server-wont-start.html) instead.) +This page explains possible reasons [a `rippled` server](xrpl-servers.html) may start successfully, but get stuck in a ["connected" state](rippled-server-states.html) without ever fully connecting to the network. (If the server crashes during or shortly after startup, see [Server Won't Start](server-wont-start.html) instead.) These instructions assume you have [installed `rippled`](install-rippled.html) on a supported platform. @@ -101,7 +101,7 @@ As a test, you can temporarily change the paths to your server's databases as lo ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Peer Protocol](peer-protocol.html) - [Technical FAQ](technical-faq.html) - **Tutorials:** diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.ja.md b/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.ja.md index 033f019ebf..39936e10e6 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.ja.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.ja.md @@ -7,7 +7,7 @@ labels: --- # rippledサーバーが起動しない -このページでは、[`rippled`サーバー](the-rippled-server.html)が起動しない際に考えられる原因とその修正方法を説明します。 +このページでは、[`rippled`サーバー](xrpl-servers.html)が起動しない際に考えられる原因とその修正方法を説明します。 以下の手順では、サポートされているプラットフォームに[`rippled`がインストール](install-rippled.html)されていることを前提としています。 @@ -205,7 +205,7 @@ ShardStore:ERR Unsupported shard store type: RocksDB ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [技術に関するよくある質問](technical-faq.html) - **チュートリアル:** - [ログメッセージについて](understanding-log-messages.html) diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.md b/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.md index 9af4ffa270..c03d223427 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.md @@ -7,7 +7,7 @@ labels: --- # rippled Server Won't Start -This page explains possible reasons [the `rippled` server](the-rippled-server.html) does not start and how to fix them. +This page explains possible reasons [the `rippled` server](xrpl-servers.html) does not start and how to fix them. These instructions assume you have [installed `rippled`](install-rippled.html) on a supported platform. @@ -206,7 +206,7 @@ To fix this problem, do one of the following, then restart the server: ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Technical FAQ](technical-faq.html) - **Tutorials:** - [Understanding Log Messages](understanding-log-messages.html) diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.ja.md b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.ja.md index 44ad920f2f..8cb4926941 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.ja.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.ja.md @@ -7,7 +7,7 @@ labels: --- # ログメッセージについて -以下のセクションでは、[`rippled`サーバー](the-rippled-server.html)のデバッグログに出力される最も一般的なログメッセージタイプとその解釈を説明します。 +以下のセクションでは、[`rippled`サーバー](xrpl-servers.html)のデバッグログに出力される最も一般的なログメッセージタイプとその解釈を説明します。 これは、`rippled`の[問題を診断する](diagnosing-problems.html)上で重要なステップです。 @@ -218,7 +218,7 @@ NetworkOPs:WRN We are not running on the consensus ledger ## 関連項目 - **コンセプト:** - - [`rippled`サーバー](the-rippled-server.html) + - [`rippled`サーバー](xrpl-servers.html) - [技術に関するよくある質問](technical-faq.html) - **チュートリアル:** - [問題の診断](diagnosing-problems.html) diff --git a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md index 3c0b8d8a73..c5fc14e8c6 100644 --- a/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md +++ b/content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md @@ -7,7 +7,7 @@ labels: --- # Understanding Log Messages -The following sections describe some of the most common types of log messages that can appear in a [`rippled` server's](the-rippled-server.html) debug log and how to interpret them. +The following sections describe some of the most common types of log messages that can appear in a [`rippled` server's](xrpl-servers.html) debug log and how to interpret them. This is an important step in [Diagnosing Problems](diagnosing-problems.html) with `rippled`. @@ -338,7 +338,7 @@ NetworkOPs:WRN We are not running on the consensus ledger ## See Also - **Concepts:** - - [The `rippled` Server](the-rippled-server.html) + - [The `rippled` Server](xrpl-servers.html) - [Technical FAQ](technical-faq.html) - **Tutorials:** - [Diagnosing Problems](diagnosing-problems.html) diff --git a/content/tutorials/use-specialized-payment-types/use-payment-channels.md b/content/tutorials/use-specialized-payment-types/use-payment-channels.md index e2f284e7d5..b2b50335bd 100644 --- a/content/tutorials/use-specialized-payment-types/use-payment-channels.md +++ b/content/tutorials/use-specialized-payment-types/use-payment-channels.md @@ -8,7 +8,7 @@ labels: --- # Use Payment Channels -[Payment Channels](payment-channels.html) are an advanced feature for sending "asynchronous" XRP payments that can be divided into very small increments and settled later. This tutorial walks through the entire process of using a payment channel, with examples using the [JSON-RPC API](rippled-api.html) of a local [`rippled` server](the-rippled-server.html). +[Payment Channels](payment-channels.html) are an advanced feature for sending "asynchronous" XRP payments that can be divided into very small increments and settled later. This tutorial walks through the entire process of using a payment channel, with examples using the [JSON-RPC API](rippled-api.html) of a local [`rippled` server](xrpl-servers.html). Ideally, to step through this tutorial, you would have two people, each with the keys to a [funded XRP Ledger account](accounts.html). However, you can also step through the tutorial as one person managing two XRP Ledger addresses. diff --git a/dactyl-config.yml b/dactyl-config.yml index 0b0a2c1bcd..0ebdd8f3f0 100644 --- a/dactyl-config.yml +++ b/dactyl-config.yml @@ -146,7 +146,7 @@ targets: # Fix link from untranslated manifest.html: "rippled-server-modes.html#reporting-mode": "rippled-server-modes.html#レポーティングモード" # Fix links for untranslated get-started-using-python.html: - "the-rippled-server.html#reasons-to-run-your-own-server": "rippled-server-modes.html#ストックサーバーを運用する理由" + "xrpl-servers.html#reasons-to-run-your-own-server": "rippled-server-modes.html#ストックサーバーを運用する理由" "cryptographic-keys.html#key-components": "cryptographic-keys.html#キーの生成" "accounts.html#addresses": "accounts.html#アドレス" "cryptographic-keys.html#private-key": "cryptographic-keys.html#キーの生成" @@ -971,83 +971,89 @@ pages: targets: - ja - - md: concepts/the-rippled-server/the-rippled-server.md + - md: concepts/xrpl-servers/xrpl-servers.md targets: - en - name: rippledサーバー - html: the-rippled-server.html + html: xrpl-servers.html parent: concepts.html template: pagetype-category.html.jinja blurb: rippledは、XRP Ledgerを管理するコアのピアツーピアサーバーです。このセクションではコンセプトについて説明します。XRP Ledgerの基本的な部分の背景に「何があるか」、「なぜなのか」を学ぶことができます。 targets: - ja - - md: concepts/the-rippled-server/rippled-server-modes.md + - md: concepts/xrpl-servers/rippled-server-modes.md targets: - en - - md: concepts/the-rippled-server/rippled-server-modes.ja.md + - md: concepts/xrpl-servers/rippled-server-modes.ja.md targets: - ja - - md: concepts/the-rippled-server/clustering.md + - md: concepts/xrpl-servers/clustering.md targets: - en - - md: concepts/the-rippled-server/clustering.ja.md + - md: concepts/xrpl-servers/clustering.ja.md targets: - ja - - md: concepts/the-rippled-server/ledger-history/ledger-history.md + - md: concepts/xrpl-servers/ledger-history/ledger-history.md targets: - en - - md: concepts/the-rippled-server/ledger-history/ledger-history.ja.md + - md: concepts/xrpl-servers/ledger-history/ledger-history.ja.md targets: - ja - - md: concepts/the-rippled-server/ledger-history/online-deletion.md + - md: concepts/xrpl-servers/ledger-history/online-deletion.md targets: - en - - md: concepts/the-rippled-server/ledger-history/online-deletion.ja.md + - md: concepts/xrpl-servers/ledger-history/online-deletion.ja.md targets: - ja - - md: concepts/the-rippled-server/ledger-history/history-sharding.md + - md: concepts/xrpl-servers/ledger-history/history-sharding.md targets: - en - - md: concepts/the-rippled-server/ledger-history/history-sharding.ja.md + - md: concepts/xrpl-servers/ledger-history/history-sharding.ja.md targets: - ja - - md: concepts/the-rippled-server/peer-protocol.md + - md: concepts/xrpl-servers/peer-protocol.md targets: - en - - md: concepts/the-rippled-server/peer-protocol.ja.md + - md: concepts/xrpl-servers/peer-protocol.ja.md targets: - ja - - md: concepts/the-rippled-server/transaction-censorship-detection.md + - md: concepts/xrpl-servers/transaction-censorship-detection.md targets: - en - - md: concepts/the-rippled-server/transaction-censorship-detection.ja.md + - md: concepts/xrpl-servers/transaction-censorship-detection.ja.md targets: - ja - - md: concepts/nodes-and-clients/the-clio-server.md + - md: concepts/xrpl-servers/the-clio-server.md targets: - en + - ja - - name: The Clio Server - html: the-clio-server.html - parent: concepts.html - template: pagetype-category.html.jinja - blurb: Clio is an XRP Ledger API server optimized for WebSocket or HTTP API calls. + # Redirect old "the-rippled-server.html" + - name: The rippled Server + html: the-rippled-server.html + template: pagetype-redirect.html.jinja + redirect_url: xrpl-servers.html + blurb: Learn about the core servers that power the XRP Ledger. + nav_omit: true + targets: + - en + - ja # Redirect old NFT articles - name: Non-fungible Tokens (NFTs) @@ -4155,7 +4161,7 @@ pages: template: page-ambassadors.html.jinja sidebar: disabled targets: - - en + - en - name: XRPL Jobs html: https://jobs.xrpl.org/