Skip to content

Use minimal configuration for fresh Ship installations - #4

Merged
im-tyler merged 1 commit into
mainfrom
fix/installer-minimal-base
Sep 27, 2026
Merged

im-tyler merged 1 commit into
mainfrom
fix/installer-minimal-base

Conversation

@im-tyler

Copy link
Copy Markdown
Contributor

Fresh installations currently merge their destination overlay with the maintainer's production configuration, inheriting unrelated host mounts and preview settings. The installer now stages the minimal self-hosted configuration with the built image inputs, applies the destination overlay there, and removes the private temporary context on exit. The source checkout is unchanged and the deployed version retains its source commit identifier.

Validation: lint passed; 1,411 runtime tests and 101 script tests passed (one existing skip). A staging test checks every Dockerfile COPY input, exact minimal-base selection, exclusion of operator files, and refusal of a nonempty destination. Shell syntax checks passed. An isolated installation rehearsal is running; clean-machine installation timing remains unverified. Production remains frozen for the ongoing baseline.

@im-tyler
im-tyler merged commit 95876fe into main Sep 27, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant