Skip to content

A local-first multi-agent app development platform, built on PenguinHarness

1.3 KB
Raw Blame
/**
 * The scripts that run on the FAR side of a machines operation, and where they come from.
 *
 * `install-server.ts` resolves them beside the module
 * that spawns it — `opts.assets?.() ?? path.dirname(import.meta.url)`. That is dist/ for a
 * packaged install and the published assets directory for a hot-pushed bundle, so the same
 * set has to be produced by two different builds: packages/server/tsup.config.ts copies them
 * into dist/, scripts/deploy.mjs pushes them as assets.
 *
 * Written once here because it was written twice before, and the copies drifted: the push
 * shipped the two installers and neither applier, leaving a hot-pushed server that could not
 * upgrade a machine or sign in to one — each dying on an ENOENT naming a path inside its own
 * store. Neither build could notice, because each list is valid on its own. Both appliers
 * have since become `penguin` subcommands the machine already has, which is the reason only
 * the installers are left: an installer is the one thing that has to arrive BEFORE the CLI
 * does.
 *
 * `from` is relative to the repository root; `name` is the flat filename both destinations
 * use, which is the name the runtime looks for.
 */
export const FAR_SIDE_SCRIPTS = [
  { name: "install.sh", from: "install.sh" },
  { name: "install.ps1", from: "install.ps1" },
];