anbaric 1.68.3 → 1.69.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/docs/features/deploying.md +13 -0
- package/package.json +5 -5
|
@@ -59,6 +59,19 @@ anbaric jobs watch <job-id> # follow a job as it progresses
|
|
|
59
59
|
more can be switched to a **large** instance (faster compute, 2× the memory,
|
|
60
60
|
$50/£50 a month instead of $20/£20, and not covered by the free allowance)
|
|
61
61
|
on the console's Manage apps page. Deploying never asks about size.
|
|
62
|
+
- **A pause on redeploy, unless you pay not to have one.** A redeploy builds the
|
|
63
|
+
new version while the old one keeps running, drains the old one (it finishes
|
|
64
|
+
the steps it has in hand, up to five minutes), then swaps the two. In the
|
|
65
|
+
ordinary case the old version is retired as soon as the new container has
|
|
66
|
+
started, which is before the app inside it is listening, so there is a gap
|
|
67
|
+
of the app's boot time in which it does not answer. **Zero-downtime
|
|
68
|
+
deploys**, switched on per app on the Manage apps page for $10/£10 a month,
|
|
69
|
+
hold the old version until the new one is answering, so the app is served
|
|
70
|
+
throughout; the switch-over is a few seconds in which a request may reach
|
|
71
|
+
either version.
|
|
72
|
+
Jobs are unaffected either way: the old version stops taking steps when it
|
|
73
|
+
is drained and the new version takes them when it is up. The setting takes
|
|
74
|
+
effect from the next deploy and is off by default. Anbaric Cloud only.
|
|
62
75
|
|
|
63
76
|
## Updating and tearing down
|
|
64
77
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "anbaric",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.69.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.69.0",
|
|
28
|
+
"anbaric-data-store": "^1.69.0",
|
|
29
|
+
"anbaric-state-machine": "^1.69.0",
|
|
30
|
+
"anbaric-tsapi": "^1.69.0"
|
|
31
31
|
}
|
|
32
32
|
}
|