-
Notifications
You must be signed in to change notification settings - Fork 76
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into flatten-getEvents
- Loading branch information
Showing
12 changed files
with
160 additions
and
77 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
name: 'Set up integration tests' | ||
description: 'Set up Go & Rust, build artifacts, work around cache issues and Ubuntu quirks' | ||
inputs: | ||
go-version: | ||
required: true | ||
runs: | ||
using: "composite" | ||
steps: | ||
- uses: ./.github/actions/setup-go | ||
with: | ||
go-version: ${{ matrix.go }} | ||
- uses: stellar/actions/rust-cache@main | ||
- name: Build soroban contract fixtures | ||
shell: bash | ||
run: | | ||
rustup update | ||
rustup target add wasm32-unknown-unknown | ||
make build_rust | ||
make build-test-wasms | ||
- name: Install Captive Core | ||
shell: bash | ||
run: | | ||
# Workaround for https://github.com/actions/virtual-environments/issues/5245, | ||
# libc++1-8 won't be installed if another version is installed (but apt won't give you a helpful | ||
# message about why the installation fails) | ||
sudo apt-get remove -y libc++1-10 libc++abi1-10 || true | ||
sudo wget -qO - https://apt.stellar.org/SDF.asc | APT_KEY_DONT_WARN_ON_DANGEROUS_USAGE=true sudo apt-key add - | ||
sudo bash -c 'echo "deb https://apt.stellar.org focal unstable" > /etc/apt/sources.list.d/SDF-unstable.list' | ||
sudo apt-get update && sudo apt-get install -y stellar-core="$PROTOCOL_20_CORE_DEBIAN_PKG_VERSION" | ||
echo "Using stellar core version $(stellar-core version)" | ||
# Docker-compose's remote contexts on Ubuntu 20 started failing with an OpenSSL versioning error. | ||
# See https://stackoverflow.com/questions/66579446/error-executing-docker-compose-building-webserver-unable-to-prepare-context-un | ||
- name: Work around Docker Compose problem | ||
shell: bash | ||
run: | | ||
sudo apt-get update | ||
sudo apt-get install -y ca-certificates curl gnupg | ||
# Install docker apt repo | ||
sudo install -m 0755 -d /etc/apt/keyrings | ||
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg | ||
sudo chmod a+r /etc/apt/keyrings/docker.gpg | ||
echo \ | ||
"deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \ | ||
"$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \ | ||
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null | ||
# Install docker-compose v2 from apt repo | ||
sudo apt-get update | ||
sudo apt-get remove -y moby-compose | ||
sudo apt-get install -y docker-compose-plugin | ||
echo "Docker Compose Version:" | ||
docker-compose version | ||
- name: Build libpreflight | ||
shell: bash | ||
run: make build-libpreflight |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,7 @@ | ||
target/ | ||
captive-core/ | ||
.soroban/ | ||
!test.toml | ||
*.sqlite | ||
|
||
cmd/crates/soroban-spec-typescript/fixtures/ts/package-lock.json |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,58 @@ | ||
# Soroban-RPC | ||
|
||
Soroban-RPC allows you to communicate directly with Soroban via a JSON RPC interface. | ||
|
||
For example, you can build an application and have it send a transaction, get ledger and event data or simulate transactions. | ||
|
||
## Dependencies | ||
- [Git](https://git-scm.com/downloads) | ||
- [Go](https://golang.org/doc/install) | ||
- [Rust](https://www.rust-lang.org/tools/install) | ||
- [Cargo](https://doc.rust-lang.org/cargo/getting-started/installation.html) | ||
|
||
## Building Stellar-Core | ||
Soroban-RPC requires an instance of stellar-core binary on the same host. This is referred to as the `Captive Core`. | ||
Since, we are building RPC from source, we recommend considering two approaches to get the stellar-core binary: | ||
- If saving time is top priority and your development machine is on a linux debian OS, then consider installing the | ||
testnet release candidates from the [testing repository.](https://apt.stellar.org/pool/unstable/s/stellar-core/) | ||
- The recommended option is to compile the core source directly on your machine: | ||
- Clone the stellar-core repo: | ||
```bash | ||
git clone https://github.com/stellar/stellar-core.git | ||
cd stellar-core | ||
``` | ||
- Fetch the tags and checkout the testnet release tag: | ||
```bash | ||
git fetch --tags | ||
git checkout tags/v20.0.0-rc.2.1 -b soroban-testnet-release | ||
``` | ||
- Follow the build steps listed in [INSTALL.md](https://github.com/stellar/stellar-core/blob/master/INSTALL.md) file for the instructions on building the local binary | ||
|
||
## Building Soroban-RPC | ||
- Similar to stellar-core, we will clone the soroban-tools repo and checkout the testnet release tag: | ||
```bash | ||
git clone https://github.com/stellar/soroban-tools.git | ||
cd soroban-tools | ||
git fetch --tags | ||
git checkout tags/v20.0.0-rc4 -b soroban-testnet-release | ||
``` | ||
- Build soroban-rpc target: | ||
```bash | ||
make build-soroban-rpc | ||
``` | ||
This will install and build the required dependencies and generate a `soroban-rpc` binary in the working directory. | ||
|
||
## Configuring and Running RPC Server | ||
- Both stellar-core and soroban-rpc require configuration files to run. | ||
- For production, we specifically recommend running Soroban RPC with a TOML configuration file rather than CLI flags. | ||
- There is a new subcommand `gen-config-file` which takes all the same arguments as the root command (or no arguments at all), | ||
and outputs the resulting config toml file to stdout. | ||
```bash | ||
./soroban-rpc gen-config-file | ||
``` | ||
- Paste the output to a file and save it as `.toml` file in any directory. | ||
- Make sure to update the config values to testnet specific ones. You can refer to [Configuring](https://docs.google.com/document/d/1SIbrFWFgju5RAsi6stDyEtgTa78VEt8f3HhqCLoySx4/edit#heading=h.80d1jdtd7ktj) section in the Runbook for specific config settings. | ||
- If everything is set up correctly, then you can run the RPC server with the following command: | ||
```bash | ||
./soroban-rpc --config-path <PATH_TO_THE_RPC_CONFIG_FILE> | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.