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

Remove currentpage.md variables

Browse Source 
As part of the Redocly migration, I'm removing syntax that isn't
compatible with the new portal. In many of these cases, the existing
if/else statements weren't working as intended anyway because they
hadn't been updated after the files had been renamed.

In the case of the Client Libraries page, I've removed mention of
editing the page to contribute client libraries for now; when someone
adds guidelines (issue #2266) it would make sense to add a link to those
guidelines in that place instead.
This commit is contained in:
mDuo13
2023-11-14 16:32:08 -08:00
parent 82da0e53a8
commit 3abbe83110
6 changed files with 8 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
content/_snippets/post-rippled-install.md
View File

@@ -2,12 +2,9 @@ It can take several minutes to sync with the rest of the XRP Ledger network, dur
You can use the [`rippled` commandline interface](get-started-using-http-websocket-apis.html#commandline) to see if your server is synced with the network:
{% if currentpage.md == "tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md" or
currentpage.md == "tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md" %}
./rippled server_info
{% else %}
/opt/ripple/bin/rippled server_info
{% endif %}
```sh
rippled server_info
```
If the `server_state` in the response is `full` or `proposing`, then your server is fully synced to the network. Otherwise, you may need to wait longer. Fresh servers usually sync within 15 minutes; servers that already have [ledger history](ledger-history.html) stored can take longer.
@@ -21,25 +18,11 @@ Having trouble getting your server started? See [rippled Server Won't Start](ser
`rippled` should connect to the XRP Ledger with the default configuration. However, you can change your settings by editing the `rippled.cfg` file. For recommendations about configuration settings, see [Capacity Planning](capacity-planning.html).
{% include '_snippets/conf-file-location.md' %}<!--_ -->
{% include '_snippets/conf-file-location.md' %}
See [the `rippled` GitHub repository](https://github.com/XRPLF/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.md" or
currentpage.md == "tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum" %}
sudo systemctl restart rippled.service
{% elif currentpage.md == "tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md" or
currentpage.md == "tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md" %}
* Use Ctrl-C to stop `rippled`, then start it again:
./rippled
{% endif %}
You must restart `rippled` for any configuration changes to take effect.
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.