Skip to content

Conversation

@amela
Copy link

@amela amela commented Oct 9, 2025

@amela amela linked an issue Oct 9, 2025 that may be closed by this pull request
@netlify
Copy link

netlify bot commented Oct 9, 2025

Deploy Preview for oasisprotocol-oasis-sdk ready!

Name Link
🔨 Latest commit 0f3e788
🔍 Latest deploy log https://app.netlify.com/projects/oasisprotocol-oasis-sdk/deploys/6947e8b74f78280008c3b40c
😎 Deploy Preview https://deploy-preview-2349--oasisprotocol-oasis-sdk.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.

@amela amela force-pushed the amela/docs-rofl-proxy-custom-domains branch 5 times, most recently from 7670f91 to c51ba27 Compare October 9, 2025 09:36
@amela amela marked this pull request as ready for review October 9, 2025 09:46
@ptrus ptrus force-pushed the amela/docs-rofl-proxy-custom-domains branch from c51ba27 to 78352ad Compare December 21, 2025 12:24
@ptrus
Copy link
Member

ptrus commented Dec 21, 2025

I have applied my suggestions. @matevz please review

@codecov
Copy link

codecov bot commented Dec 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.55%. Comparing base (394da33) to head (0f3e788).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2349   +/-   ##
=======================================
  Coverage   48.54%   48.55%           
=======================================
  Files         224      224           
  Lines       16079    16079           
=======================================
+ Hits         7806     7807    +1     
+ Misses       8213     8212    -1     
  Partials       60       60           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ptrus ptrus force-pushed the amela/docs-rofl-proxy-custom-domains branch from 78352ad to 0f3e788 Compare December 21, 2025 12:31
services in your app. Simply publish a port in your `compose.yaml` and the
proxy handles TLS certificates and routing.
The ROFL proxy automatically generates public HTTPS URLs for services in your
ROFL app. Simply publish a port in your `compose.yaml` and the proxy handles
Copy link
Member

Choose a reason for hiding this comment

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

Please avoid using "ROFL app" and use either "ROFL" or "app".

Suggested change
ROFL app. Simply publish a port in your `compose.yaml` and the proxy handles
app. Simply publish a port in your `compose.yaml` and the proxy handles

@@ -1,10 +1,10 @@
# Port Proxy
# ROFL Proxy
Copy link
Member

Choose a reason for hiding this comment

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

Don't repeat ROFL in the title, because the whole part is devoted to ROFL. I'd leave the title alone or maybe change it simply to # Proxy.

Suggested change
# ROFL Proxy
# Port Proxy

TLS certificates and routing.

TLS is terminated inside the app, providing end-to-end encryption so that
TLS is terminated inside the ROFL app, providing end-to-end encryption so that
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
TLS is terminated inside the ROFL app, providing end-to-end encryption so that
TLS is terminated inside the app, providing end-to-end encryption so that

```
After deploying your app, you can find the generated URL by
After deploying your ROFL app, you can find the generated URL by
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
After deploying your ROFL app, you can find the generated URL by
After deploying your ROFL, you can find the generated URL by

route through the proxy.

When using `custom_domain`, you must verify ownership of the domain and complete the
routing setup. After your ROFL app is deployed, use the Oasis CLI to obtain setup
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
routing setup. After your ROFL app is deployed, use the Oasis CLI to obtain setup
routing setup. After your app is deployed, use the Oasis CLI to obtain setup


`<published_port>` — the external port exposed in your compose.yaml

`<setting>` — the specific proxy configuration (e.g., mode, custom_domain)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
`<setting>` — the specific proxy configuration (e.g., mode, custom_domain)
`<setting>` — the specific proxy configuration (e.g., `mode`, `custom_domain`)

Port proxy for your ROFL automatically generates public HTTPS URLs for
services in your app. Simply publish a port in your `compose.yaml` and the
proxy handles TLS certificates and routing.
The ROFL proxy automatically generates public HTTPS URLs for services in your
Copy link
Member

Choose a reason for hiding this comment

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

This isn't true for passthrough mode anymore.

Comment on lines +80 to +82
#### `mode`

`net.oasis.proxy.ports.<published_port>.mode`
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
#### `mode`
`net.oasis.proxy.ports.<published_port>.mode`
#### `net.oasis.proxy.ports.<published_port>.mode`

Comment on lines +92 to +94
#### `custom_domain`

`net.oasis.proxy.ports.<published_port>.custom_domain`
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
#### `custom_domain`
`net.oasis.proxy.ports.<published_port>.custom_domain`
#### `net.oasis.proxy.ports.<published_port>.custom_domain`


What this configuration does:
- The application container exposes ports 8080 and 80.
- On port 8080 the proxy forwards the raw TCP connection to your application container (mode: passthrough).
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- On port 8080 the proxy forwards the raw TCP connection to your application container (mode: passthrough).
- On port 8080 the proxy forwards the raw TCP connection to your application container (`mode: passthrough`).

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.

docs: Document ROFL proxy custom domains

4 participants