querysub 0.263.0 → 0.264.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/package.json
CHANGED
|
@@ -714,7 +714,8 @@ export class Querysub {
|
|
|
714
714
|
Querysub.trustedDomains.add(domain);
|
|
715
715
|
}
|
|
716
716
|
|
|
717
|
-
|
|
717
|
+
// Hot reloading on public servers breaks things when we update (as the git pull triggers a hot reload), so... don't do that.
|
|
718
|
+
if (config.hotReload && !isPublic()) {
|
|
718
719
|
watchFilesAndTriggerHotReloading();
|
|
719
720
|
}
|
|
720
721
|
|
|
@@ -1,21 +1,28 @@
|
|
|
1
|
+
7) Broken loading of CYOA
|
|
2
|
+
1) Deploy (database functions)
|
|
3
|
+
2) deploy the CYOA service
|
|
4
|
+
3) Refresh the main page
|
|
5
|
+
RESULT: It tries to access the specific hash, but it wasn't loaded serverside, so permissions are refused
|
|
1
6
|
|
|
2
7
|
8) Fix deploy user notification issue, where the refresh button doesn't work?
|
|
3
8
|
- For application level updates
|
|
4
9
|
- Just an application commit, then deploy the service, then the refresh button should show up, and work
|
|
5
10
|
|
|
6
11
|
|
|
7
|
-
What about cloudflare registration?
|
|
8
12
|
8) Use a special service for the HTTP bootstrapper, and then have 2 others that are on other ports
|
|
9
|
-
- Find a way to prevent the bootstrapper from being picked as the backend as well, so we don't need to update it!
|
|
10
|
-
|
|
11
13
|
--bootstraponly is added, and should work?
|
|
12
14
|
|
|
15
|
+
9) Verify the bootstrap server can't be picked as the endpoint server
|
|
16
|
+
|
|
17
|
+
|
|
13
18
|
9) Rolling service updates
|
|
14
19
|
- Add rollingWindow to the definition
|
|
15
20
|
- Set for public facing services (but not for scripts)
|
|
16
21
|
- PathValueServer - 10 minutes
|
|
17
22
|
- FunctionRunner - 10 minutes
|
|
18
23
|
- HTTP - 4 hours
|
|
24
|
+
- Boostrapper - NO rolling
|
|
25
|
+
- gc/join - NO rolling
|
|
19
26
|
- Show the rolling time in the update buttons (both list and the save button on the details page), so we know it will be a rolling update
|
|
20
27
|
- Keep the oldest service alive when we update
|
|
21
28
|
- Tracked per serviceId
|
|
@@ -30,3 +37,6 @@ What about cloudflare registration?
|
|
|
30
37
|
- Filled, but the total size will also depend on the maximum (to a degree), so it's very nice.
|
|
31
38
|
- A bar, with a label, or something. The AI can give us a few options
|
|
32
39
|
(Yes, it overlaps with node metrics, but that's okay, sometimes we want to look at machines, other times services, and the types of errors that show up in either changes).
|
|
40
|
+
|
|
41
|
+
|
|
42
|
+
11) Restart the server and verify everything starts up nicely on reboot!
|