Upgrade to v2.3.0

[Normalnoise]

Swan Provider v2.3.0 release

Highlights!

Please see release log

How to upgrade to v2.3.0?

Scenario One

• If you are a new user, you can install and config the go-swan-provider following this instruction.

Scenario Two

If you have installed the previous version, you can upgrade to the latest version v2.3.0 by following the steps:

(1) Stop your swan-provider

(2) Set your $SWAN_PATH: export SWAN_PATH="/data/.swan", default ~/.swan

(3) Install and Run the new version swan-provider:

Option 1️⃣ : Prebuilt package

wget --no-check-certificate https://raw.githubusercontent.com/filswan/go-swan-provider/release-2.3.0/install.sh
chmod +x ./install.sh
./install.sh

# Start the swan-provider
ulimit -SHn 1048576
export SWAN_PATH = "/data/.swan"
nohup swan-provider-2.3.0-linux-amd64 daemon >> swan-provider.log 2>&1 & 

Option 2️⃣ : Source code

git clone https://github.com/filswan/go-swan-provider.git
cd go-swan-provider
git checkout release-2.3.0
./build_from_source.sh

# Start the swan-provider
ulimit -SHn 1048576
export SWAN_PATH = "/data/.swan"
nohup swan-provider daemon >> swan-provider.log 2>&1 & 

Note:

• If you set a different $SWAN_PATH, you need to reconfigure your configuration according to the steps
• If you set the same $SWAN_PATH, the old configuration file will be backed up in the $SWAN_PATH when you build and install the swan-provider

Scenario Three

If you have run the boostd to import the deals, you can receive the deals from filswan by the following steps:

(1) Install the swan-provider according to the section
(2) Move your boostd repo to the $SWAN_PATH and move the boostd binary to the /usr/local/bin/:

mkdir $SWAN_PATH/provider/boost
mv ~/.boost/* $SWAN_PATH/provider/boost/

mv boostd /usr/local/bin/

(3) Config the config.toml according to the section

‼️ ‼️ Note: If you are upgrading from previous version of Boostd, you must add localIndexDirectory.Leveldb in the boost config file.

vi $SWAN_PATH/provider/boost/config.toml

[localIndexDirectory.Leveldb]
Enabled = true

(4) Run the swan-provider in the background.

ulimit -SHn 1048576
export SWAN_PATH = "/data/.swan"
nohup swan-provider daemon >> swan-provider.log 2>&1 & 

Do you have questions?

Please leave a comment.

[Shekelme]

Sure we have questions.

1. When will swan-provider finally be able to communicate with boostd installed and configured according to it's own instructions? Why should we move boostd repo anywhere?
2. Why must we enable Leveldb if we wish to work with officially and highly recommended YugabyteDB? How should it all work if I already use YugabyteDB for boostd's local index directory and then I'll suddenly enable leveldb?

[Normalnoise]

@Shekelme thanks for your question, for current stage, swan provider communicate with official boostd, so you can follow the boost official instructions or directly use the binary provided by swan team. we have our own boost instruction, and we have maintained customized boost, this version is internal use only now. For the most SP, just download the boostd binary from swan provider release is enough, swan provider will automatically install and config the boostd.

so sorry this version just support LevelDB, it is enough for most SP, swan provider is a open source project, if you are interested in the yugaDB feature, welcome discussion and contributions

[ratohe]

"so sorry this version just support LevelDB, it is enough for most SP" vs Total Storage Provider 2,468----Active StorageProvider 46. I think most SPs, including me, can't downgrade to LevelDB.

[ratohe]

Any news about yugabyteDB integration?

[ratohe]

Just tested, works fine with yugabyte.

[Normalnoise]

great, the new version v2.4.0 has support the yugaDB