@haakco/hostingctl 1.0.310 → 1.0.312

package/dist/main.js

@@ -24745,7 +24745,11 @@ var hostingWorkloadServerModeEnumSchema = _enum(["shared", "dedicated"]).describ
 var createHostingEnvironmentRequestSchema = object({
 	certificateIssuer: hostingCertificateIssuerEnumSchema.optional(),
 	applicationLayout: _enum(["dedicated"]).optional().describe("How an environment's web applications are served. `DEDICATED` preserves existing environments and initial Node workload sets: one Pod per application, each with its own CPU and memory limits. Existing layouts never change merely because a new creation default is released.  `SHARED_WORDPRESS` is plan 40's layout: one Apache/mod_php container serves every WordPress application in the environment, and each member keeps its own tree, Service, Ingress, certificate and database identity. The container carries the SUM of its members' limits.  `SHARED_APPLICATIONS` is plan 48's layout and a superset of the WordPress case: one Pod holds the WordPress container AND one container per Moodle application, with the aggregate CPU/memory ceiling on the POD and no per-container limit, so WordPress may borrow capacity Moodle is not using and the reverse. It is a separate value rather than a reinterpretation of `SHARED_WORDPRESS`, because an environment that adopted WordPress sharing never consented to moving its Moodle applications into that Pod.  `SHARED_ENVIRONMENT` is the new PHP environment default: web, cron, Redis and tools share one parent cap with requests-only containers. MariaDB remains separate. Component settings are persisted at creation or explicit adoption and read from PostgreSQL thereafter.  `SHARED_PHP` is the shared environment with **one** PHP container instead of one container per PHP application: the same web, cron, Redis and tools Pod, but the Apache/PHP container serves every WordPress AND Moodle member as vhosts. N PHP applications then cost about one runtime's memory instead of N runtimes'. It is a value of its own rather than a change to `SHARED_APPLICATIONS` or `SHARED_ENVIRONMENT`, because an environment already composing those layouts keeps composing them exactly as before; a member joins the one container only in an environment that selected this.  The stored value is this case's name, so a layout is a value the platform declares and validates rather than a branch keyed by a string somewhere.\n"),
-	resourceProfile: _enum(["small_sites", "empty_environment"]).optional(),
+	resourceProfile: _enum([
+		"small_sites",
+		"empty_environment",
+		"low_end"
+	]).optional(),
 	name: string().max(100),
 	slug: string().min(3).max(63).regex(/^[a-z0-9]([a-z0-9-]*[a-z0-9])?$/),
 	budget: object({
@@ -36508,7 +36512,7 @@ function writeUpdateState(state, env = process.env) {
 }
 //#endregion
 //#region src/version.ts
-var VERSION = "0.0.0-dev";
+var VERSION = "1.0.312";
 //#endregion
 //#region src/commands/update.ts
 /**
@@ -36583,7 +36587,7 @@ var update = {
 		}, process.env);
 		return {
 			...known,
-			current: after ?? "0.0.0-dev",
+			current: after ?? "1.0.312",
 			latest: after ?? latest,
 			upToDate: after !== null && (latest === null || !isNewerVersion(latest, after)),
 			action: "run",
@@ -36821,6 +36825,13 @@ function startsWith(path, prefix) {
 	return prefix.every((one, index) => path[index] === one);
 }
 /**
+* How long the notice waits for the lock that guards the state file.
+*
+* Short, because the notice runs beside a command a person is waiting on: a machine that is busy updating
+* its session is not a reason to hold this one up, and the check simply happens again next time.
+*/
+var NOTICE_LOCK_WAIT_MS = 150;
+/**
 * Tell the client, once a day, that a newer version is published.
 *
 * The notice goes to stderr, so it never mixes into a command's output, and it names `hostingctl update`
@@ -36829,6 +36840,34 @@ function startsWith(path, prefix) {
 */
 async function printUpdateNotice(options) {
 	if (options.json) return;
+	const env = options.env ?? process.env;
+	if (isSet(env.CI)) return;
+	if (isSet(env.HOSTINGCTL_NO_UPDATE_CHECK)) return;
+	const state = readUpdateState(env);
+	const now = Date.now();
+	if (state !== null && now - state.checkedAt < 864e5) return;
+	const latest = await latestVersion();
+	try {
+		mkdirSync(credentialDirectory(env), {
+			recursive: true,
+			mode: 448
+		});
+		await withCredentialLock(async () => {
+			writeUpdateState({
+				method: state?.method ?? null,
+				entry: state?.entry ?? "",
+				checkedAt: now,
+				latest
+			}, env);
+		}, env, { waitMs: NOTICE_LOCK_WAIT_MS });
+	} catch {}
+	if (latest === null) return;
+	if (!isNewerVersion(latest, "1.0.312")) return;
+	process.stderr.write(`A newer hostingctl is published: ${latest} (this copy is ${VERSION}). Run \`hostingctl update\` to update.\n`);
+}
+/** Whether an environment variable is set to something, which is how CI and the opt-out are read. */
+function isSet(value) {
+	return value !== void 0 && value !== "";
 }
 //#endregion
 //#region src/main.ts