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

1.3.1 supersedes 1.3.0

Browse Source
This commit is contained in:
mDuo13
2019-07-25 15:37:07 -07:00
parent 9c46187253
commit 7287c3d70b
11 changed files with 26 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/_snippets/rippled_versions.md
View File

@@ -35,4 +35,4 @@
[New in: rippled 1.1.0]: https://github.com/ripple/rippled/releases/tag/1.1.0 "BADGE_BLUE"
[New in: rippled 1.2.0]: https://github.com/ripple/rippled/releases/tag/1.2.0 "BADGE_BLUE"
[New in: rippled 1.2.1]: https://github.com/ripple/rippled/releases/tag/1.2.1 "BADGE_BLUE"
[New in: rippled 1.3.0]: https://github.com/ripple/rippled/releases/tag/1.3.0 "BADGE_BLUE"
[New in: rippled 1.3.1]: https://github.com/ripple/rippled/releases/tag/1.3.1 "BADGE_BLUE"

2
content/concepts/consensus-network/amendments/known-amendments.md
View File

@@ -9,7 +9,7 @@ The following is a comprehensive list of all known amendments and their status o
| [OwnerPaysFee][] | TBD | [In Development: TBD]( "BADGE_LIGHTGREY") |
| [SHAMapV2][] | TBD | [In Development: TBD]( "BADGE_LIGHTGREY") |
| [Tickets][] | TBD | [In Development: TBD]( "BADGE_LIGHTGREY") |
| [fixMasterKeyAsRegularKey][] | v1.3.0 | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [fixMasterKeyAsRegularKey][] | v1.3.1 | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [Checks][] | v0.90.0 | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [FlowCross][] | v0.70.0 | [Planned: TBD]( "BADGE_LIGHTGREY") |
| [MultiSignReserve][] | v1.2.0 | [Enabled: 2019-04-17](https://xrpcharts.ripple.com/#/transactions/C421E1D08EFD78E6B8D06B085F52A34A681D0B51AE62A018527E1B8F54C108FB "BADGE_GREEN") |

2
content/tutorials/manage-the-rippled-server/configuration/configure-history-sharding.md
View File

@@ -33,7 +33,7 @@ path=/var/lib/rippled/db/shards/nudb
max_size_gb=50
```
The `type` field can be omitted. If present, it _MUST_ be `NuDB`. [New in: rippled 1.3.0][]
The `type` field can be omitted. If present, it _MUST_ be `NuDB`. [New in: rippled 1.3.1][]
**Caution:** If `rippled` detects the wrong type of data in the shard store path, it may [fail to start](server-wont-start.html). You should use a new folder for the shard store. If you previously used a RocksDB shard store (`rippled` 1.2.x and lower), use a different path or delete the RocksDB shard data.

2
content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md
View File

@@ -24,7 +24,7 @@ For development purposes Ripple recommends running `rippled` as your own user, n
$ brew install git cmake pkg-config protobuf openssl ninja
0. Install Boost 1.70.0 or higher. `rippled` 1.3.0 is compatible with Boost 1.70.0 and higher. The latest version of Boost available in the Homebrew repositories isn't new enough, so you must install Boost manually:
0. Install Boost 1.70.0 or higher. `rippled` 1.3.1 is compatible with Boost 1.70.0 and higher. The latest version of Boost available in the Homebrew repositories isn't new enough, so you must install Boost manually:
1. Download [Boost 1.70.0](https://dl.bintray.com/boostorg/release/1.70.0/source/boost_1_70_0.tar.bz2).

13
content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md
View File

@@ -31,7 +31,7 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof
4. Install CMake.
Version 1.3.0 of `rippled` requires CMake 3.9.0 or higher. For the purposes of this tutorial, we used CMake 3.13.3, which was the latest version available at the time of writing.
Version 1.3.1 of `rippled` requires CMake 3.9.0 or higher. For the purposes of this tutorial, we used CMake 3.13.3, which was the latest version available at the time of writing.
If you have previously installed CMake 3.9.0 or higher, you can skip these steps.
@@ -44,7 +44,7 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof
5. Compile Boost.
Version 1.3.0 of `rippled` requires Boost version 1.70.0 or higher. Because Boost version 1.70.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself.
Version 1.3.1 of `rippled` requires Boost version 1.70.0 or higher. Because Boost version 1.70.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself.
If you have previously built Boost 1.70.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps.
@@ -88,11 +88,12 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof
$ git log -1
commit caa5c9e2232ff1eee1d0c61907283649e48e6fbc
Author: Nik Bougalis <nikb@bougalis.net>
Date: Tue Jul 9 13:56:37 2019 -0700
commit e1adbd7ddd5dfa9f2a9791aa3c0fcc1fdb4e8236
Author: Manoj doshi <mdoshi@ripple.com>
Date: Wed Jul 24 15:21:56 2019 -0700
Set version to 1.3.1
Set version to 1.3.0
8. If you previously built, or (more importantly) tried and failed to build `rippled`, you should delete the `my_build/` directory (or whatever you named it) to start clean before moving on to the next step. Otherwise, you may get unexpected behavior, like a `rippled` executable that crashes due to a segmentation fault (segfault).

2
content/tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum.md
View File

@@ -32,7 +32,7 @@ Before you install `rippled`, you must meet the [System Requirements](system-req
$ sudo yum install rippled
Version 1.3.0 does not require any changes to your config files (`rippled.cfg` and `validators.txt`). This update procedure leaves your existing config files in place.
Version 1.3.1 does not require any changes to your config files (`rippled.cfg` and `validators.txt`). This update procedure leaves your existing config files in place.
4. Reload systemd unit files:

2
content/tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu.md
View File

@@ -1,6 +1,6 @@
# Install on Ubuntu or Debian Linux
This page describes the recommended instructions for installing the latest stable version of `rippled` on **Ubuntu Linux 16.04 or higher** or **Debian 9 (Stretch)**, using the [`apt`](https://help.ubuntu.com/lts/serverguide/apt.html) utility. [Updated in: rippled 1.3.0][New in: rippled 1.3.0]
This page describes the recommended instructions for installing the latest stable version of `rippled` on **Ubuntu Linux 16.04 or higher** or **Debian 9 (Stretch)**, using the [`apt`](https://help.ubuntu.com/lts/serverguide/apt.html) utility. [Updated in: rippled 1.3.1][New in: rippled 1.3.1]
These instructions install a binary that has been compiled by Ripple.

14
content/tutorials/manage-the-rippled-server/installation/rippled-1-3-0-migration-instructions.md → content/tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.md
View File

@@ -1,6 +1,6 @@
# rippled v1.3.0 Migration Instructions
# rippled v1.3.x Migration Instructions
This document describes the migration process for upgrading from `rippled` 1.2.4 or earlier to `rippled` v1.3.0 or later. This migration process is necessary because the `rippled` install process has changed as of version 1.3.0.
This document describes the migration process for upgrading from `rippled` 1.2.4 or earlier to `rippled` v1.3 or later. This migration process is necessary because the `rippled` install process has changed as of version 1.3.
This document provides migration steps for upgrading on supported platforms:
@@ -22,7 +22,7 @@ Ripple's official RPM repository and instructions for using it have changed. If
$ sudo rpm -e ripple-repo
The `rippled-repo` package is **DEPRECATED** as of `rippled` version 1.3.0. The package has been updated one last time for 1.3.0. In the future, any changes to the repositories will require manual changes to your repos file.
The `rippled-repo` package is now **DEPRECATED**. The package has been updated one last time for version 1.3.1. In the future, any changes to the repositories will require manual changes to the `ripple.repo` file.
3. Add Ripple's new yum repository:
@@ -40,7 +40,7 @@ Ripple's official RPM repository and instructions for using it have changed. If
$ sudo yum install rippled
Version 1.3.0 does not require any changes to your config files (`rippled.cfg` and `validators.txt`). This update procedure leaves your existing config files in place.
Version 1.3.1 does not require any changes to your config files (`rippled.cfg` and `validators.txt`). This update procedure leaves your existing config files in place.
5. Reload systemd unit files:
@@ -56,9 +56,9 @@ Ripple's official RPM repository and instructions for using it have changed. If
## Migration on Ubuntu Linux
Prior to version 1.3.0, the supported way to install `rippled` on Ubuntu Linux was using Alien to install the RPM package. Starting with `rippled` v1.3.0, Ripple provides a native package for Ubuntu and Debian Linux, which is the recommended way of installing it. If you already have the RPM package installed, complete the [installation steps](install-rippled-on-ubuntu.html) to upgrade the package and switch over to the native APT (`.deb`) package.
Prior to version 1.3, the supported way to install `rippled` on Ubuntu Linux was using Alien to install the RPM package. Starting with `rippled` v1.3.1, Ripple provides a native package for Ubuntu and Debian Linux, which is the recommended way of installing it. If you already have the RPM package installed, complete the [installation steps](install-rippled-on-ubuntu.html) to upgrade the package and switch over to the native APT (`.deb`) package.
If you have made any changes to your config files (`/opt/ripple/etc/rippled.cfg` and `/opt/ripple/etc/validators.txt`), `apt` may prompt you during installation asking if you want to overwrite your config files with the newest versions from the packages. Version 1.3.0 does not require any changes to the config file, so you can safely keep your existing config files unchanged.
If you have made any changes to your config files (`/opt/ripple/etc/rippled.cfg` and `/opt/ripple/etc/validators.txt`), `apt` may prompt you during installation asking if you want to overwrite your config files with the newest versions from the packages. Version 1.3 does not require any changes to the config file, so you can safely keep your existing config files unchanged.
After installing the new package, if you no longer need Alien for any other packages, you may optionally uninstall it and its dependencies using the following steps:
@@ -73,4 +73,4 @@ After installing the new package, if you no longer need Alien for any other pack
### Automatic Updates
The `rippled` v1.3.0 package includes an updated auto-update script that works on Ubuntu and Debian Linux. For more information, see [Update `rippled` Automatically on Linux](update-rippled-automatically-on-linux.html).
The `rippled` v1.3 package includes an updated auto-update script that works on Ubuntu and Debian Linux. For more information, see [Update `rippled` Automatically on Linux](update-rippled-automatically-on-linux.html).

4
content/tutorials/manage-the-rippled-server/installation/update-rippled-manually-on-ubuntu.md
View File

@@ -2,9 +2,9 @@
This page describes how to update manually to the latest release of `rippled` on Ubuntu Linux. These instructions assume you have already [installed `rippled` using the native package](install-rippled-on-ubuntu.html). Ripple recommends setting up [automatic updates](update-rippled-automatically-on-linux.html) instead, where possible.
**Caution:** To upgrade from `rippled` 1.2.x to 1.3.0 or higher on Ubuntu Linux, you should follow the [1.3.0 migration instructions](rippled-1-3-0-migration-instructions.html). The following instructions assume you have already installed the native APT package provided with versions 1.3.0 and up.
**Caution:** To upgrade from `rippled` 1.2.x to 1.3.1 or higher on Ubuntu Linux, you should follow the [1.3.1 migration instructions](rippled-1-3-0-migration-instructions.html). The following instructions assume you have already installed the native APT package provided with versions 1.3.1 and up.
**Tip:** To perform these steps all at once, you can run the `/opt/ripple/bin/update-rippled.sh` script, which is included with the `rippled` package and is compatible with Ubuntu and Debian starting with `rippled` version 1.3.0.
**Tip:** To perform these steps all at once, you can run the `/opt/ripple/bin/update-rippled.sh` script, which is included with the `rippled` package and is compatible with Ubuntu and Debian starting with `rippled` version 1.3.1.
To update manually, complete the following steps:

2
content/tutorials/manage-the-rippled-server/troubleshooting/server-wont-start.md
View File

@@ -181,7 +181,7 @@ If your config includes a `[shard_db]` stanza, it must contain a `path` field, w
## Unsupported shard store type: RocksDB
RocksDB is no longer supported as a backend for [history sharding](history-sharding.html). If you have an existing configuration that defines a RocksDB shard store, the server fails to start. [New in: rippled 1.3.0][]
RocksDB is no longer supported as a backend for [history sharding](history-sharding.html). If you have an existing configuration that defines a RocksDB shard store, the server fails to start. [New in: rippled 1.3.1][]
In this case, the process dies shortly after the log startup command, with a message such as the following appearing earlier in the output log:

6
dactyl-config.yml
View File

@@ -1109,13 +1109,13 @@ pages:
targets:
- local
- md: tutorials/manage-the-rippled-server/installation/rippled-1-3-0-migration-instructions.md
html: rippled-1-3-0-migration-instructions.html
- md: tutorials/manage-the-rippled-server/installation/rippled-1-3-migration-instructions.md
html: rippled-1-3-migration-instructions.html
funnel: Docs
doc_type: Tutorials
category: Manage the rippled Server
subcategory: Installation
blurb: Use these instructions to upgrade rippled packages from 1.2.x or below to 1.3.0 or higher.
blurb: Use these instructions to upgrade rippled packages from 1.2.x or below to 1.3.x or higher.
targets:
- local