mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-17 18:25:50 +00:00
Backport post-install stuff from the macos PR to reorg PR
This commit is contained in:
@@ -25,21 +25,25 @@ Having trouble getting your `rippled` server started? See [rippled Server Won't
|
|||||||
|
|
||||||
See [the `rippled` GitHub repository](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) for a description of all configuration options.
|
See [the `rippled` GitHub repository](https://github.com/ripple/rippled/blob/master/cfg/rippled-example.cfg) for a description of all configuration options.
|
||||||
|
|
||||||
|
You must restart `rippled` for any configuration changes to take effect:
|
||||||
|
|
||||||
|
|
||||||
{% if currentpage.md == "tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu-with-alien.md" or
|
{% if currentpage.md == "tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu-with-alien.md" or
|
||||||
currentpage.md == "tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum" %}
|
currentpage.md == "tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum" %}
|
||||||
If you change the `[debug_logfile]` or `[database_path]` sections, you may need to grant the `rippled` user and group ownership to your new configured path:
|
$ sudo systemctl restart rippled.service
|
||||||
|
|
||||||
```
|
{% elif currentpage.md == "tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md" or
|
||||||
$ chown -R rippled:rippled <configured path>
|
currentpage.md == "tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md" %}
|
||||||
```
|
|
||||||
|
|
||||||
Restart `rippled` for any configuration changes to take effect:
|
* Use Ctrl-C to stop `rippled`, then start it again:
|
||||||
|
|
||||||
|
$ ./rippled
|
||||||
|
|
||||||
```
|
|
||||||
$ sudo service rippled restart
|
|
||||||
```
|
|
||||||
{% endif %}
|
{% endif %}
|
||||||
|
|
||||||
|
If you change the `[debug_logfile]` or `[database_path]` sections, you may need to grant ownership of the new configured path to the user you run `rippled` as.
|
||||||
|
|
||||||
|
|
||||||
### Updates
|
### Updates
|
||||||
|
|
||||||
You must update `rippled` regularly to remain synced with the rest of the XRP Ledger network. You can subscribe to the [rippled Google Group](https://groups.google.com/forum/#!forum/ripple-server) to receive notifications of new `rippled` releases.
|
You must update `rippled` regularly to remain synced with the rest of the XRP Ledger network. You can subscribe to the [rippled Google Group](https://groups.google.com/forum/#!forum/ripple-server) to receive notifications of new `rippled` releases.
|
||||||
|
|||||||
@@ -0,0 +1,56 @@
|
|||||||
|
# Connect Your rippled to the XRP Test Net
|
||||||
|
|
||||||
|
Ripple has created the [XRP Test Network](https://ripple.com/build/xrp-test-net/) to provide a testing platform for the XRP Ledger. XRP Test Net funds are not real funds and are intended for testing only. You can connect your `rippled` server to the XRP Test Net to test out and understand `rippled` functionality before connecting to the production XRP Ledger Network. You can also use the XRP Test Net to verify that your own code interacts correctly with `rippled`.
|
||||||
|
|
||||||
|
**Note:** The XRP Test Net ledger and balances are reset on a regular basis.
|
||||||
|
|
||||||
|
To connect your `rippled` server to the XRP Test Net, set the following configurations:
|
||||||
|
|
||||||
|
1. In your `rippled.cfg` file:
|
||||||
|
|
||||||
|
a. Uncomment the following section, as follows:
|
||||||
|
|
||||||
|
[ips]
|
||||||
|
r.altnet.rippletest.net 51235
|
||||||
|
|
||||||
|
b. Comment out the following section, as follows:
|
||||||
|
|
||||||
|
# [ips]
|
||||||
|
# r.ripple.com 51235
|
||||||
|
|
||||||
|
2. In your `validators.txt` file:
|
||||||
|
|
||||||
|
a. Uncomment the following sections, as follows:
|
||||||
|
|
||||||
|
[validator_list_sites]
|
||||||
|
https://vl.altnet.rippletest.net
|
||||||
|
|
||||||
|
[validator_list_keys]
|
||||||
|
ED264807102805220DA0F312E71FC2C69E1552C9C5790F6C25E3729DEB573D5860
|
||||||
|
|
||||||
|
b. Comment out the following sections, as follows:
|
||||||
|
|
||||||
|
# [validator_list_sites]
|
||||||
|
# https://vl.ripple.com
|
||||||
|
#
|
||||||
|
# [validator_list_keys]
|
||||||
|
# ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734
|
||||||
|
|
||||||
|
3. Restart `rippled`.
|
||||||
|
|
||||||
|
4. To verify that your `rippled` is connected to the XRP Test Net, use the [server_info method][] on your server and compare it to the results from a public server on the Test Net. 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 command checks the latest validated ledger of a Test Net server at `s.altnet.rippletest.net`:
|
||||||
|
|
||||||
|
$ ./rippled --rpc_ip 34.210.87.206:51234 server_info | grep seq
|
||||||
|
|
||||||
|
The following command checks your local `rippled`'s latest validated ledger sequence:
|
||||||
|
|
||||||
|
$ ./rippled server_info | grep seq
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<!--{# common link defs #}-->
|
||||||
|
{% include '_snippets/rippled-api-links.md' %}
|
||||||
|
{% include '_snippets/tx-type-links.md' %}
|
||||||
|
{% include '_snippets/rippled_versions.md' %}
|
||||||
@@ -1003,6 +1003,16 @@ pages:
|
|||||||
targets:
|
targets:
|
||||||
- local
|
- local
|
||||||
|
|
||||||
|
- md: tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md
|
||||||
|
html: connect-your-rippled-to-the-xrp-test-net.html
|
||||||
|
funnel: Docs
|
||||||
|
doc_type: Tutorials
|
||||||
|
category: Manage the rippled Server
|
||||||
|
subcategory: Configuration
|
||||||
|
blurb: Connect your rippled server to the test net to try out new features or test functionality with fake money.
|
||||||
|
targets:
|
||||||
|
- local
|
||||||
|
|
||||||
- md: tutorials/manage-the-rippled-server/configuration/cluster-rippled-servers.md
|
- md: tutorials/manage-the-rippled-server/configuration/cluster-rippled-servers.md
|
||||||
html: cluster-rippled-servers.html
|
html: cluster-rippled-servers.html
|
||||||
funnel: Docs
|
funnel: Docs
|
||||||
|
|||||||
Reference in New Issue
Block a user