rays/ipx
1
0
Fork 0
Code Issues 11 Pull Requests Actions Packages Projects Releases 20 Wiki Activity

docs/play.md: the tunnel and traces reach ipx-play through the host's address

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ray Slakinski
2026-11-13 14:35:52 +00:00
parent ac246682f0
commit c133adf398
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/play.md
View File

@@ -31,7 +31,7 @@ The compose service, beside `ipx-directory`:
env_file: play.env # PLAY_DATABASE_URL=postgres://...
environment:
PLAY_LOG_FORMAT: json
OTEL_EXPORTER_OTLP_ENDPOINT: http://tempo:4318
OTEL_EXPORTER_OTLP_ENDPOINT: http://192.168.1.130:4318 # Tempo is not on this network
volumes:
- /mnt/fast/appdata/ipx-play:/config
ports:
@@ -56,8 +56,9 @@ Its database is Postgres, `ipx_play` on the `databases` project's server, its UR
beside the compose file (mode 600), as the directory's is. It makes its one table, `shares`, on
start.
The tunnel publishes `play.ipxreader.app` to `http://ipx-play:8102` with no Access in front: the
pages are anyone's. `/v1` takes a token for everything.
The tunnel publishes `play.ipxreader.app` to `http://192.168.1.130:8102` with no Access in front:
the pages are anyone's. cloudflared is not on the project's network, so not `ipx-play:8102`, as
the directory's route is the host's port too. `/v1` takes a token for everything.
## Setting up ipx