devlanes 0.5.0 → 0.6.1

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "devlanes",
3
- "version": "0.5.0",
3
+ "version": "0.6.1",
4
4
  "description": "Development environments in Git worktree lanes",
5
5
  "license": "Apache-2.0",
6
6
  "homepage": "https://devlanes.run",
@@ -30,11 +30,11 @@
30
30
  "node": ">=18"
31
31
  },
32
32
  "optionalDependencies": {
33
- "@devlanes/darwin-arm64": "0.5.0",
34
- "@devlanes/darwin-x64": "0.5.0",
35
- "@devlanes/linux-arm64": "0.5.0",
36
- "@devlanes/linux-x64": "0.5.0",
37
- "@devlanes/win32-arm64": "0.5.0",
38
- "@devlanes/win32-x64": "0.5.0"
33
+ "@devlanes/darwin-arm64": "0.6.1",
34
+ "@devlanes/darwin-x64": "0.6.1",
35
+ "@devlanes/linux-arm64": "0.6.1",
36
+ "@devlanes/linux-x64": "0.6.1",
37
+ "@devlanes/win32-arm64": "0.6.1",
38
+ "@devlanes/win32-x64": "0.6.1"
39
39
  }
40
40
  }
package/schema.json CHANGED
@@ -1989,6 +1989,25 @@
1989
1989
  ],
1990
1990
  "markdownDescription": "Hostnames the devlanes HTTPS proxy routes to this service, so `https://<host>` reaches it. One entry or a list; an entry is a hostname or a mapping with `host` and optional `port` (a named port), `fallback` and `host_header`. A `*.` wildcard matches subdomains, and an exact host wins over it. The first non-wildcard host becomes `public_url`, non-wildcard hosts join the lane's `DEVLANES_ORIGINS`, and having hosts makes the default `ready` a TCP check. Keep them under `${{ lane.domain }}` so lanes do not collide."
1991
1991
  },
1992
+ "keep_awake": {
1993
+ "anyOf": [
1994
+ {
1995
+ "$ref": "#/$defs/Templated_boolean",
1996
+ "description": "",
1997
+ "examples": [],
1998
+ "markdownDescription": ""
1999
+ },
2000
+ {
2001
+ "type": "null"
2002
+ }
2003
+ ],
2004
+ "description": "While this service runs, devlanes never throttles or freezes its lane, whatever `lanes.throttle_after` and `lanes.freeze_after` in the user config say. Set it on workers, queue consumers, schedulers and tunnels that do work without inbound requests, which a frozen lane would otherwise stall. One such service keeps the whole lane awake. An expression is evaluated for each lane, such as `${{ lane.index == 0 }}` to keep only the main lane awake. Defaults to false.",
2005
+ "examples": [
2006
+ true,
2007
+ false
2008
+ ],
2009
+ "markdownDescription": "While this service runs, devlanes never throttles or freezes its lane, whatever `lanes.throttle_after` and `lanes.freeze_after` in the user config say. Set it on workers, queue consumers, schedulers and tunnels that do work without inbound requests, which a frozen lane would otherwise stall. One such service keeps the whole lane awake. An expression is evaluated for each lane, such as `${{ lane.index == 0 }}` to keep only the main lane awake. Defaults to false."
2010
+ },
1992
2011
  "name": {
1993
2012
  "description": "Label shown in the TUI and human output instead of the service key; any text, spaces allowed, with ` #N` added per replica. Commands, profiles and `${{ services.<key> }}` keep using the key.",
1994
2013
  "examples": [
package/user-schema.json CHANGED
@@ -1088,13 +1088,21 @@
1088
1088
  },
1089
1089
  "UserLanesConfig": {
1090
1090
  "additionalProperties": false,
1091
- "description": "Machine settings for lanes. Each lane gets its own data folder at `<data_dir>/<project>/<lane id>`, available as `${{ lane.data_path }}` and `DEVLANES_LANE_DATA`. devlanes creates it when the lane is created and before each start, and `devlanes lane clean` deletes it.",
1091
+ "description": "Machine settings for lanes: where their data folders live, and when idle lanes are throttled or frozen. Each lane gets its own data folder at `<data_dir>/<project>/<lane id>`, available as `${{ lane.data_path }}` and `DEVLANES_LANE_DATA`. devlanes creates it when the lane is created and before each start, and `devlanes lane clean` deletes it.",
1092
1092
  "examples": [
1093
1093
  {
1094
1094
  "data_dir": "~/.devlanes/data"
1095
+ },
1096
+ {
1097
+ "freeze_after": "15m",
1098
+ "throttle_after": "5m"
1099
+ },
1100
+ {
1101
+ "freeze_after": "1h",
1102
+ "throttle_after": "0s"
1095
1103
  }
1096
1104
  ],
1097
- "markdownDescription": "Machine settings for lanes. Each lane gets its own data folder at `<data_dir>/<project>/<lane id>`, available as `${{ lane.data_path }}` and `DEVLANES_LANE_DATA`. devlanes creates it when the lane is created and before each start, and `devlanes lane clean` deletes it.",
1105
+ "markdownDescription": "Machine settings for lanes: where their data folders live, and when idle lanes are throttled or frozen. Each lane gets its own data folder at `<data_dir>/<project>/<lane id>`, available as `${{ lane.data_path }}` and `DEVLANES_LANE_DATA`. devlanes creates it when the lane is created and before each start, and `devlanes lane clean` deletes it.",
1098
1106
  "properties": {
1099
1107
  "data_dir": {
1100
1108
  "default": null,
@@ -1108,6 +1116,27 @@
1108
1116
  "string",
1109
1117
  "null"
1110
1118
  ]
1119
+ },
1120
+ "freeze_after": {
1121
+ "$ref": "#/$defs/ConfigDuration",
1122
+ "default": "900000ms",
1123
+ "description": "After this long without activity, devlanes freezes a lane: it suspends every process of the lane and pauses the lane's own containers. Shared infra is never paused. Ports and process state are kept, so a frozen lane still counts as running. Activity is a request through the proxy, a new connection to one of the lane's ports, the lane's services using CPU, or a devlanes command on the lane; any of it resumes a frozen lane and restarts the timer. A request through the proxy resumes the lane at once and then goes through; a direct connection to a port is noticed within about half a second. When both are set above `0s`, it must be longer than `throttle_after` (`5m` unless set). A running service with `services.<name>.keep_awake: true` keeps its whole lane awake. Defaults to `15m`; `0s` turns freezing off. The daemon reads it when it starts.",
1124
+ "examples": [
1125
+ "15m",
1126
+ "1h",
1127
+ "0s"
1128
+ ],
1129
+ "markdownDescription": "After this long without activity, devlanes freezes a lane: it suspends every process of the lane and pauses the lane's own containers. Shared infra is never paused. Ports and process state are kept, so a frozen lane still counts as running. Activity is a request through the proxy, a new connection to one of the lane's ports, the lane's services using CPU, or a devlanes command on the lane; any of it resumes a frozen lane and restarts the timer. A request through the proxy resumes the lane at once and then goes through; a direct connection to a port is noticed within about half a second. When both are set above `0s`, it must be longer than `throttle_after` (`5m` unless set). A running service with `services.<name>.keep_awake: true` keeps its whole lane awake. Defaults to `15m`; `0s` turns freezing off. The daemon reads it when it starts."
1130
+ },
1131
+ "throttle_after": {
1132
+ "$ref": "#/$defs/ConfigDuration",
1133
+ "default": "300000ms",
1134
+ "description": "After this long without activity, a lane's processes run at background priority: lower CPU priority, and efficiency cores on machines that have them. They keep serving requests. Activity is a request through the proxy, a new connection to one of the lane's ports, the lane's services using CPU, or a devlanes command on the lane; any of it restores normal priority and restarts the timer. macOS and Windows only; Linux has no throttling, so lanes there stay at normal priority until `freeze_after`. When both are set above `0s`, it must be shorter than `freeze_after`. A running service with `services.<name>.keep_awake: true` keeps its whole lane at normal priority. Defaults to `5m`; `0s` turns throttling off. The daemon reads it when it starts.",
1135
+ "examples": [
1136
+ "5m",
1137
+ "0s"
1138
+ ],
1139
+ "markdownDescription": "After this long without activity, a lane's processes run at background priority: lower CPU priority, and efficiency cores on machines that have them. They keep serving requests. Activity is a request through the proxy, a new connection to one of the lane's ports, the lane's services using CPU, or a devlanes command on the lane; any of it restores normal priority and restarts the timer. macOS and Windows only; Linux has no throttling, so lanes there stay at normal priority until `freeze_after`. When both are set above `0s`, it must be shorter than `freeze_after`. A running service with `services.<name>.keep_awake: true` keeps its whole lane at normal priority. Defaults to `5m`; `0s` turns throttling off. The daemon reads it when it starts."
1111
1140
  }
1112
1141
  },
1113
1142
  "type": "object"
@@ -1185,15 +1214,25 @@
1185
1214
  "lanes": {
1186
1215
  "$ref": "#/$defs/UserLanesConfig",
1187
1216
  "default": {
1188
- "data_dir": null
1217
+ "data_dir": null,
1218
+ "freeze_after": "900000ms",
1219
+ "throttle_after": "300000ms"
1189
1220
  },
1190
- "description": "Where lane data folders (`lane.data_path`) live on this machine.",
1221
+ "description": "Where lane data folders (`lane.data_path`) live on this machine, and how long a lane may sit without activity before devlanes throttles or freezes it.",
1191
1222
  "examples": [
1192
1223
  {
1193
1224
  "data_dir": "~/.devlanes/data"
1225
+ },
1226
+ {
1227
+ "freeze_after": "15m",
1228
+ "throttle_after": "5m"
1229
+ },
1230
+ {
1231
+ "freeze_after": "1h",
1232
+ "throttle_after": "0s"
1194
1233
  }
1195
1234
  ],
1196
- "markdownDescription": "Where lane data folders (`lane.data_path`) live on this machine."
1235
+ "markdownDescription": "Where lane data folders (`lane.data_path`) live on this machine, and how long a lane may sit without activity before devlanes throttles or freezes it."
1197
1236
  },
1198
1237
  "logs": {
1199
1238
  "$ref": "#/$defs/LogsConfig",