Skip to content

Commit 2cbdfd6

Browse files
fix(cli): t3 status no longer suggests --no-lan under a T3CODE_HOST override
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent fc93f26 commit 2cbdfd6

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎apps/server/src/cli/up.ts‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ interface Setup {
4242
/** T3 Connect revoked the link; `t3 connect` links again. */
4343
readonly connectRevoked: boolean;
4444
readonly lan: boolean;
45-
/** An installed service with no T3CODE_LAN keeps the old default: on. */
45+
/** An installed service with no T3CODE_LAN or T3CODE_HOST keeps the old default: on. */
4646
readonly lanFromOldDefault: boolean;
4747
readonly host: string | undefined;
4848
}
@@ -86,7 +86,7 @@ const readSetup = Effect.fn("cli.up.read_setup")(function* () {
8686
connect,
8787
connectRevoked,
8888
lan: Option.getOrElse(lan, () => servesThisHome),
89-
lanFromOldDefault: Option.isNone(lan) && servesThisHome,
89+
lanFromOldDefault: Option.isNone(lan) && servesThisHome && entries.T3CODE_HOST === undefined,
9090
host: entries.T3CODE_HOST,
9191
} satisfies Setup;
9292
});

0 commit comments

Comments
 (0)