@hyperlogue/r3 2.2.0 → 2.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +17 -1
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -102,7 +102,20 @@ on the home page to archive or permanently delete them together.
|
|
|
102
102
|
|
|
103
103
|
## Local and remote access
|
|
104
104
|
|
|
105
|
-
r3 starts a local server automatically when needed.
|
|
105
|
+
r3 starts a local server automatically when needed. It listens only on this
|
|
106
|
+
computer and needs no login by default; the browser explains the trade-off the
|
|
107
|
+
first time. Artifact links returned by agents stay stable, so they keep working
|
|
108
|
+
later. Run `r3 config set requireLogin true` to require login locally; servers
|
|
109
|
+
reachable from other machines always require it.
|
|
110
|
+
|
|
111
|
+
Configuring an external hostname in `publicUrl` or `allowedHosts`, or adding
|
|
112
|
+
`trustedProxies`, enables login by default, even when the proxy connects through
|
|
113
|
+
localhost. The default local-only mode refuses forwarded requests. Use
|
|
114
|
+
`r3 config set requireLogin true` to require login explicitly, or
|
|
115
|
+
`r3 config set requireLogin false` to disable browser and API authentication for
|
|
116
|
+
all allowed hosts. `r3 config unset requireLogin` restores the automatic default.
|
|
117
|
+
Run `r3 server restart` on the server's machine after changing these settings.
|
|
118
|
+
Host/origin checks and preview isolation apply in both modes.
|
|
106
119
|
|
|
107
120
|
### Expose an r3 server
|
|
108
121
|
|
|
@@ -141,5 +154,8 @@ your terminal, and approve CLI access. Then check the connection:
|
|
|
141
154
|
r3 list
|
|
142
155
|
```
|
|
143
156
|
|
|
157
|
+
Remote CLI backends require `r3 login` even when the server has browser login
|
|
158
|
+
disabled. This authorizes the CLI to send publications to that backend.
|
|
159
|
+
|
|
144
160
|
Ask your agent to run `r3 guide` and publish as usual. See the
|
|
145
161
|
[remote backend reference](docs/artifacts/remote-protocol.md) for more options.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@hyperlogue/r3",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.3.0",
|
|
4
4
|
"description": "Render. Review. Refine. — publish artifacts and discuss them with any coding agent. Runs the matching prebuilt native r3 binary (shipped as a per-platform optional dependency); works with `bunx @hyperlogue/r3` and `npx @hyperlogue/r3`.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -17,10 +17,10 @@
|
|
|
17
17
|
"launch.mjs"
|
|
18
18
|
],
|
|
19
19
|
"optionalDependencies": {
|
|
20
|
-
"@hyperlogue/r3-darwin-arm64": "2.
|
|
21
|
-
"@hyperlogue/r3-darwin-x64": "2.
|
|
22
|
-
"@hyperlogue/r3-linux-x64": "2.
|
|
23
|
-
"@hyperlogue/r3-linux-arm64": "2.
|
|
20
|
+
"@hyperlogue/r3-darwin-arm64": "2.3.0",
|
|
21
|
+
"@hyperlogue/r3-darwin-x64": "2.3.0",
|
|
22
|
+
"@hyperlogue/r3-linux-x64": "2.3.0",
|
|
23
|
+
"@hyperlogue/r3-linux-arm64": "2.3.0"
|
|
24
24
|
},
|
|
25
25
|
"engines": {
|
|
26
26
|
"node": ">=18"
|