Valist publish on non-CI/CD environments requires a mechanism for reproducible build environments about valist HOT 4 CLOSED

some thoughts on the format for the valist.yml and how to keep config consistent between desktop/CI

in the valist.yml file, we'll need the following keys:

image: DOCKER_IMAGE
install: INSTALL_COMMAND
build: BUILD_COMMAND
out: OUTPUT_DIR_OR_FILE_INSIDE_CONTAINER

the build and install commands are optional if the image that is set already builds what's needed for out

after image is set, we run the install command, then the build command provided inside of a new container (or build a new image from the supplied one). then, we mount and copy the out directory on the container that contains the artifact, and copy it to the host + publish.

image could also be set to the location of a Dockerfile that's already in the repository, and the rest of the flow stays the same.

eventually, we could/should use a system like buildpacks.io that would auto-detect the package type and start with the relevant container image.

from valist.

To that end, maybe something like:

const generateDockerfile = (baseImage: string, source: string, buildCommand: string) =>  ` 
  FROM ${baseImage}
  WORKDIR /opt/build
  CP ${source} ./
  WORKDIR /opt/build/${source}
  RUN ${buildCommand}
`;

from valist.

Oh and +1 to the buildpacks.io, we should add that to the roadmap.

from valist.

Closed by #28

from valist.