anbaric 1.50.0 → 1.52.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.
|
@@ -46,6 +46,26 @@ unrouted absolute path that arrives with a `Referer` from your app is redirected
|
|
|
46
46
|
back to `/app/<name>/…` (a `307`, so form POSTs keep their body). So ordinary
|
|
47
47
|
absolute links followed from a page of your app just work.
|
|
48
48
|
|
|
49
|
+
## Your app's own hostname
|
|
50
|
+
|
|
51
|
+
Every app also answers on a hostname of its own:
|
|
52
|
+
|
|
53
|
+
```
|
|
54
|
+
https://<app>--<tenant>.<platform domain>
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
There your app is at the root, exactly where it was when you ran it locally, so
|
|
58
|
+
absolute paths, `fetch("/api/…")` and anything else that assumes the root work
|
|
59
|
+
without being rewritten. This is the address to share and the one to prefer; the
|
|
60
|
+
`/app/<name>` form below stays available and unchanged.
|
|
61
|
+
|
|
62
|
+
The tenant is part of the name because two tenants may each have a `hello-world`.
|
|
63
|
+
A double hyphen separates the two, so an app name may not contain one, and the
|
|
64
|
+
app and tenant together must fit the 63 characters a hostname label allows. A
|
|
65
|
+
deploy that would break either rule is refused with the reason.
|
|
66
|
+
|
|
67
|
+
## Under /app/<name>
|
|
68
|
+
|
|
49
69
|
The exception is when the browser sends no `Referer` (for example under a strict
|
|
50
70
|
`Referrer-Policy: no-referrer`). For guaranteed correctness in that case, either:
|
|
51
71
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "anbaric",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.52.0",
|
|
4
4
|
"description": "Everything needed to write an Anbaric app: state machines, jobs, document and secret stores, local in-memory implementations and the Anbaric Cloud clients",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -24,9 +24,9 @@
|
|
|
24
24
|
"prepublishOnly": "npm run build"
|
|
25
25
|
},
|
|
26
26
|
"dependencies": {
|
|
27
|
-
"anbaric-impl-cloud": "^1.
|
|
28
|
-
"anbaric-data-store": "^1.
|
|
29
|
-
"anbaric-state-machine": "^1.
|
|
30
|
-
"anbaric-tsapi": "^1.
|
|
27
|
+
"anbaric-impl-cloud": "^1.52.0",
|
|
28
|
+
"anbaric-data-store": "^1.52.0",
|
|
29
|
+
"anbaric-state-machine": "^1.52.0",
|
|
30
|
+
"anbaric-tsapi": "^1.52.0"
|
|
31
31
|
}
|
|
32
32
|
}
|