r
/
bootstrap
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
CLI for initializing projects in a configurable way.
7 Commits
1 Branch
4 Tags
397 KiB
C 57.7%
Nix 28.2%
Shell 10.5%
CMake 2.2%
Python 1%
Other 0.4%
 
 
 
 
 
 
Go to file
Joshua Potter be95ee0fc5 Add config tests. 2023-11-23 04:09:58 -07:00
include Add config tests. 2023-11-23 04:09:58 -07:00
specs/clang Add example of spec and explanation on how it works. 2023-11-22 14:39:27 -07:00
src Add config tests. 2023-11-23 04:09:58 -07:00
test Add config tests. 2023-11-23 04:09:58 -07:00
.envrc Initial commit. 2023-11-22 10:43:05 -07:00
.gitignore Add config tests. 2023-11-23 04:09:58 -07:00
Makefile Add config tests. 2023-11-23 04:09:58 -07:00
README.md Better naming throughout to match `spec`. 2023-11-22 14:55:55 -07:00
flake.lock Add example `main.c` file. 2023-11-22 11:50:15 -07:00
flake.nix Better naming throughout to match `spec`. 2023-11-22 14:55:55 -07:00
main.c Better naming throughout to match `spec`. 2023-11-22 14:55:55 -07:00

README.md

spec

CLI utility for initializing projects in reproducible ways.

Overview

Within the specs directory exists so-called specs. A spec is a directory containing a spec.json file and a run.sh file. The former is configured like so:

{
  versions: [...],
}

The keys of this top-level JSON object correspond to the parameters that are prompted by the spec init curses interface. The value is used to determine what kind of prompt spec provides for the given question. Possible value types include:

  • [...] (list)
    • This indicates a select option prompt. The user chooses amongst the values specified in the JSON list.

Once all prompts are evaluated, the keys of the object are converted into uppercase environment variables and passed to the run.sh file relative to the current directory.