@studiometa/forge-cli 0.5.4 → 0.5.5

package/README.md

@@ -218,7 +218,7 @@ A worker or a scheduled job matches the file when its command, directory, proces
 - Without the `workers` key, no worker is read or deleted. With `"workers": []`, all the workers of the site are deleted. The same applies to `schedule`.
 - The site, its aliases, its database and its `.env` keys are never deleted.
 
-`loadBalancer` sends the traffic of the load balancer to the server of the file. The site of the load balancer is the one named `domain` or one of the `aliases`. When no site matches, `--check` and `apply` exit `3` before any change. When two sites match, they exit `3` too. The Forge API cannot create a site on a load balancer: create it in Forge (New site on the load balancer), with its certificate. To move a site to another server, change `server`: `apply` creates the site there, then moves the node, with no DNS change. It does not delete the site on the old server.
+`loadBalancer` sends the traffic of the load balancer to the server of the file. The site of the load balancer is the one named `domain` or one of the `aliases`. When no site matches, `--check` and `apply` exit `3` before any change. When two sites match, they exit `3` too. The Forge API cannot create a site on a load balancer: create it in Forge (New site on the load balancer), with its certificate. The DNS points to the load balancer, so a change of node needs no DNS change. To move a site to another server, do not only change `server`: `apply` would send the traffic to the new site at once, before its first deployment and without its data. Declare the new server in a second site file without `loadBalancer`, deploy and test it, then move `loadBalancer` to that file. Only one site file declares `loadBalancer` for a site: with the key in two files, each `apply` replaces the node of the other.
 
 With `--check`, `apply` prints the plan and changes nothing. It exits `0` when Forge matches the file, `1` when it differs, and another code on an error (`3` for an invalid file). Every deletion shows its ID and full command. The plan gives `.env` key names only, never values, and shows a generated password as `<generated>`. With `--format json`, it prints `{ "inSync": false, "changes": [...], "warnings": [...] }`.
 

package/dist/cli.js

@@ -5566,6 +5566,9 @@ async function applySiteFile(file, serverId, ctx, options = {}) {
 			server_id: serverId,
 			type: file.type,
 			name: file.domain,
+			domain_mode: "custom",
+			www_redirect_type: "none",
+			allow_wildcard_subdomains: false,
 			...settings.php_version ? { php_version: settings.php_version } : {},
 			...settings.web_directory ? { web_directory: settings.web_directory } : {},
 			...settings.source_control_provider ? { source_control_provider: settings.source_control_provider } : {},
@@ -6796,7 +6799,7 @@ function isVersionRequest({ command, options }) {
 }
 //#endregion
 //#region src/cli.ts
-var VERSION = "0.5.4";
+var VERSION = "0.5.5";
 function showHelp() {
 	console.log(`
 ${colors.bold("forge")} v${VERSION}