Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

testserver: Standalone Greenlight testserver for non-python projects #539

Merged
merged 4 commits into from
Nov 25, 2024

Conversation

cdecker
Copy link
Collaborator

@cdecker cdecker commented Nov 7, 2024

This uses the gl-testing library, and builds a standalone server to
test against. We currently expose four interfaces:

  • The scheduler interface as the main entrypoint to the service
  • The GRPC-Web proxy to develop browser apps and extensions against
    Greenlight.
  • The bitcoind interface, so you can generate blocks and confirm
    transactions without lengthy wait times
  • The node's grpc interface directly to work against a single user's
    node

All of these will listen to random ports initially. We write a small
file metadata.json which contains the URIs and ports for the first
three, while the node's URI can be retrieved from the scheduler, since
these are spawned on demand as users register.

Depends #536

@cdecker cdecker force-pushed the 202445-gl-testing-standalone branch 3 times, most recently from b84c574 to 37c934d Compare November 7, 2024 16:50
@cdecker cdecker changed the title 202445 gl testing standalone testserver: Standalone Greenlight testserver for non-python projects Nov 7, 2024
@cdecker cdecker force-pushed the 202445-gl-testing-standalone branch from 37c934d to 35aa8eb Compare November 7, 2024 17:38
This uses the `gl-testing` library, and builds a standalone server to
test against. We currently expose four interfaces:

 - The scheduler interface as the main entrypoint to the service
 - The GRPC-Web proxy to develop browser apps and extensions against
   Greenlight.
 - The `bitcoind` interface, so you can generate blocks and confirm
   transactions without lengthy wait times
 - The node's grpc interface directly to work against a single user's
   node

All of these will listen to random ports initially. We write a small
file `metadata.json` which contains the URIs and ports for the first
three, while the node's URI can be retrieved from the scheduler, since
these are spawned on demand as users register.
The TLD is the root for the tree of resources we are going to spawn,
so making this configurable allows us to run arbitrarily many
instances on a single developer machine. This is useful if we'd like
to run many tests in parallel.
@cdecker cdecker enabled auto-merge (rebase) November 22, 2024 10:55
@cdecker
Copy link
Collaborator Author

cdecker commented Nov 22, 2024

Github is having a bad day, returning a 502 error to me pressing the Confirm rebase and merge button, which is expected to be JSON. I'll wait for this to be fixed or I'll open a new PR with these contents.

@cdecker cdecker enabled auto-merge (rebase) November 25, 2024 12:31
@cdecker cdecker merged commit 6176468 into main Nov 25, 2024
12 checks passed
@cdecker cdecker deleted the 202445-gl-testing-standalone branch November 25, 2024 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant