infra/quickstart

:ID: bbb86596-4be5-4f5e-8854-9ea28b077879

1. bootstrap.sh

bootstrap.svg

The easiest way to get started is to run the top-level script bootstrap.sh. Running the script will:

  • run check.sh
  • install the latest cores and lisp runtime from https://packy.compiler.company to the stash
  • load autogen.lisp and call the function infra/autogen:autogen
    • check and apply the host config and profile
    • build all features in parallel
infra-bootstrap.gif

Upon completion a local stash directory is provisioned. At this point we no longer need to depend on shell scripting as we have a fully interactive Lisp environment to hack on our builds with.

From here, you may run skel inspect to inspect the infra skelfile and select a target to build on your machine or in a container. Use skel --help for a list of other commands.

1.1. check.sh

This script checks that the current host is qualified. It needs to be ran once before the autogen.lisp file is loaded, usually via bootstrap.sh.

This will interrogate the system, checking for minimum requirements. If any requirement isn't met an error is signaled. On completion, the name of an SXP file is printed which contains the host config.

The minimum software dependencies above should be installed via your system's package manager. 

./check.sh

1.2. autogen.lisp

Once a core and lisp runtime are available, we load autogen.lisp and call infra/autogen:autogen. This will process the host configuration (zor.sxp in the example above) and the profile (defaults to default.sxp), update environment variables for the current shell and take any additional actions needed.

The order of operations are loosely as follows:

  • initialize profile
  • update host environment variables
  • check features and ensure host dependencies
  • initialize host
  • initialize infra skelfile
  • process all features
  • quit

2. TODO deploy.lisp

Deploy infra builds to a remote.

Deployment involves 'packing' a target found in stash, archiving it, compressing it, and sending it to a remote location possibly with a signature, checksum, or other metadata, and possibly encrypted. A 'package' may also be a raw directory of plain-text files. It's a very loose term. Where the package ends up and how it is packed depends on the build-config and skelfile slots.

Production deployments end up at https://packy.compiler.company.

3. TODO install.lisp

Install core packages locally.