Skip to content

Conversation

hajjimo
Copy link
Contributor

@hajjimo hajjimo commented Aug 1, 2025

  • Addresses issue docs: Add a deployment guide using Test Network #3419

  • Related issues linked using fixes #number

  • Tests added/updated

  • Make sure that all checks pass

  • Bruno collection updated (if necessary)

  • Documentation issue created with user-docs label (if necessary)

  • OpenAPI specs updated (if necessary)

Copy link

netlify bot commented Aug 1, 2025

Deploy Preview for brilliant-pasca-3e80ec ready!

Name Link
🔨 Latest commit 78cb805
🔍 Latest deploy log https://app.netlify.com/projects/brilliant-pasca-3e80ec/deploys/689da5cfbc07d000083a0371
😎 Deploy Preview https://deploy-preview-3586--brilliant-pasca-3e80ec.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions bot added the pkg: documentation Changes in the documentation package. label Aug 1, 2025
@hajjimo hajjimo requested review from bosbaber, golobitch and beniaminmunteanu and removed request for bosbaber, golobitch and beniaminmunteanu August 1, 2025 19:46
Copy link

github-actions bot commented Aug 1, 2025

🚀 Performance Test Results

Test Configuration:

  • VUs: 4
  • Duration: 1m0s

Test Metrics:

  • Requests/s: 39.81
  • Iterations/s: 13.28
  • Failed Requests: 0.00% (0 of 2396)
📜 Logs

> performance@1.0.0 run-tests:testenv /home/runner/work/rafiki/rafiki/test/performance
> ./scripts/run-tests.sh -e test "-k" "-q" "--vus" "4" "--duration" "1m"

Cloud Nine GraphQL API is up: http://localhost:3101/graphql
Cloud Nine Wallet Address is up: http://localhost:3100/
Happy Life Bank Address is up: http://localhost:4100/
cloud-nine-wallet-test-backend already set
cloud-nine-wallet-test-auth already set
happy-life-bank-test-backend already set
happy-life-bank-test-auth already set
     data_received..................: 865 kB 14 kB/s
     data_sent......................: 1.8 MB 31 kB/s
     http_req_blocked...............: avg=7.36µs   min=2.41µs   med=5.61µs   max=1.41ms   p(90)=6.61µs   p(95)=7.14µs  
     http_req_connecting............: avg=706ns    min=0s       med=0s       max=1.09ms   p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=99.74ms  min=6.89ms   med=87.47ms  max=566.44ms p(90)=169.64ms p(95)=195.42ms
       { expected_response:true }...: avg=99.74ms  min=6.89ms   med=87.47ms  max=566.44ms p(90)=169.64ms p(95)=195.42ms
     http_req_failed................: 0.00%  ✓ 0         ✗ 2396
     http_req_receiving.............: avg=95.29µs  min=25.71µs  med=82.94µs  max=1.65ms   p(90)=121.43µs p(95)=152.48µs
     http_req_sending...............: avg=40.09µs  min=9.85µs   med=30.35µs  max=3.16ms   p(90)=43.58µs  p(95)=57.54µs 
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=99.61ms  min=6.77ms   med=87.35ms  max=566.32ms p(90)=169.53ms p(95)=195.3ms 
     http_reqs......................: 2396   39.813177/s
     iteration_duration.............: avg=300.82ms min=181.03ms med=291.65ms max=1.14s    p(90)=366.4ms  p(95)=396.89ms
     iterations.....................: 799    13.276598/s
     vus............................: 4      min=4       max=4 
     vus_max........................: 4      min=4       max=4 

@hajjimo hajjimo changed the title Mi/3419/rafiki testnet deploy docs: mi/3419/rafiki testnet deploy Aug 1, 2025
@hajjimo
Copy link
Contributor Author

hajjimo commented Aug 1, 2025

Backend test is failing, which may be related to the issue Max posted about in the #rafiki-team channel in Slack.

The preview link does display the updates:

Deployment Example (new menu item )
--> Overview (01-architecture-overview.mdx)
--> Configuration variables (02-configuration-variables.mdx)
--> Secrets management (03-services-management.mdx)
--> Infrastructure setup (04-infrastructure-setup.mdx)
--> Services deployment (05-services-deployment.mdx)
--> Troubleshooting (06-troubleshooting.mdx)

@github-actions github-actions bot added type: tests Testing related pkg: backend Changes in the backend package. type: source Changes business logic labels Aug 6, 2025
@github-actions github-actions bot removed type: tests Testing related pkg: backend Changes in the backend package. type: source Changes business logic labels Aug 6, 2025
@hajjimo hajjimo marked this pull request as ready for review August 6, 2025 11:35
]
},
{
label: 'Deployment example',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My gut says that the deployment example should be a child section under Deploy Rafiki, but let's talk about that later, when you're ready to merge.

Copy link
Contributor Author

@hajjimo hajjimo Aug 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree it should be a child section under Deploy Rafiki. I made it a different section in anticipation of the end-to-end guide for the wallet app. However, I wonder if the team will feel that this guide is unnecessary once the wallet guide is available, because the Test network architecture shouldn't be suggested as a production deployment.

- **Auth server** (`auth.your-wallet.com`): Handles <LinkOut href='openpayments.dev'>Open Payments</LinkOut> authentication and authorization
- **Backend** (`backend.your-wallet.com`): Core Interledger protocol implementation
- **Admin API** (`admin.your-wallet.com`): Administrative functions and account management via GraphQL API
- **Database**: Stores Interledger accounts, payment pointers, and transaction data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should wallet addresses be part of this, too? I'm not sure if this is for payment pointers only, since it's Interledger.

Copy link
Contributor Author

@hajjimo hajjimo Aug 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. I'll update this to wallet addresses instead.

| `project_id` | - | Yes | GCP Project ID where resources will be created |
| `region` | `us-central1` | No | Primary GCP region for cluster and resources |
| `cluster_name` | `rafiki-wallet-cluster` | No | Name of the GKE cluster |
| `domain_name` | - | Yes | Primary domain for your wallet (e.g., `mywallet.com`) |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you move this higher in the table, so the two required variables are one after the other?


<div class="overflow-table">

| Record Type | Name | Value | TTL |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a thought - Since all the record types are A records, you might be able to change the section title from DNS record configuration to DNS A record configuration (I can see how that may look a bit odd) and get rid of the Record Type column completely.

- `YOUR_PROJECT_ID` - Replace with your GCP project ID
- `YOUR_REGISTRY` - Replace with your container registry
- `YOUR_EMAIL` - Replace with your administrative email
- `<generated-secret>` - Generate using `openssl rand -base64 32` (see Secrets Management guide)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link to Secrets Management guide


Your deployed services are available at these URLs:

| Service | URL | Purpose |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the items in the URL column be wrapped in back ticks? I'm not saying they should be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: documentation Changes in the documentation package. user-docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants