ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-28 15:45:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Get Started organization updates

Browse Source 
- Split off "Public Servers" page
- Rename and reorder getting started pages by language
This commit is contained in:
mDuo13
2021-05-07 17:38:31 -07:00
parent f39c4bfeb2
commit f7cf44073c
12 changed files with 118 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md
View File

@@ -122,7 +122,7 @@ $ sudo systemctl restart rippled
It takes about 5 to 15 minutes to sync to the network after a restart. After your server is synced, the [server_info method][] shows the a `validated_ledger` object based on the network you are connected to.
To verify that your `rippled` is connected to the XRP Testnet or Devnet, compare the results from your server to [a public server](get-started-with-the-rippled-api.html#public-servers) on the Testnet or Devnet. The `seq` field of the `validated_ledger` object should be the same on both servers (possibly off by one or two, if it changed as you were checking).
To verify that your `rippled` is connected to the XRP Testnet or Devnet, compare the results from your server to [a public server][public servers] on the Testnet or Devnet. The `seq` field of the `validated_ledger` object should be the same on both servers (possibly off by one or two, if it changed as you were checking).
The following example shows how to check the latest validated ledger from the commandline:
@@ -158,7 +158,7 @@ $ rippled --rpc_ip 34.201.59.230:51234 server_info | grep seq
<!-- MULTICODE_BLOCK_END -->
**Note:** The IP addresses in these examples are for public servers, and may change periodically. If you get no response, look up the IP address of a [public server](get-started-with-the-rippled-api.html#public-servers), for example using the `dig` command.
**Note:** The IP addresses in these examples are for public servers, and may change periodically. If you get no response, look up the IP address of a [public server][public servers], for example using the `dig` command.