Application and OS setup
Day-1 setup for Seal Apps and Seal OS — the two products that seal packages inside your build.
Last updated
Day-1 setup for Seal Apps and Seal OS — the two products that seal packages inside your build.
This section covers the day-1 mechanics for the two Seal products that work at the dependency layer: Seal Apps (your application's open-source dependencies) and Seal OS (OS-level packages and language runtimes). Both products work by sealing packages inside a build, in contrast to the container-layer products covered under Container and image setup.
Choosing your deployment method: the decision page comparing the five deployment methods (Remote, Local, Automatic Remediation, Artifact Server, Manual).
Seal Apps via the Seal CLI in CI/CD: the recommended deployment — installing the CLI, fix modes, per-CI-system integration, Dockerfile patterns, local development.
Seal Apps via the Seal Artifact Server: pointing your package manager at the Seal Artifact Server as a remote.
Seal OS in CI/CD: the seal fix --os command, sealing OS packages in a Dockerfile, container build pipelines.
On-prem and air-gapped environments: hosting patterns when neither the Seal CLI nor the artifact server can reach the public internet.
Last updated