c5c586ff71
since `.dagger` directories have a special meaning now because of gitflow, it's better not to have a `~/.dagger` since it's not a workspace and it confuses dagger (e.g. `dagger new` from $HOME). We don't store state there anymore, just keys and the last version check, so it's okay to be in ~/.config IMO Looking at my system, in ~/.config there's `gcloud`, `gatsby`, `gh`, `yarn`, and others so it seems like a pretty common location. Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com> |
||
|---|---|---|
| .. | ||
| cli | ||
| compute | ||
| examples/react/.dagger/env/default | ||
| ops | ||
| stdlib | ||
| cli.bats | ||
| compute.bats | ||
| examples.bats | ||
| helpers.bash | ||
| ops.bats | ||
| package.json | ||
| README.md | ||
| stdlib.bats | ||
| yarn.lock | ||
Testing
TL;DR
# Install dependancies
yarn install
# Install gnu parallel if needed
# macOS
brew install parallel
# Debian derivatives
# apt-get install parallel
# Install sops if needed
# macOS
brew install sops
# Run all tests
yarn test
By default, the dagger binary is expected to be found in ../cmd/dagger/dagger relative to the tests directory.
If you need to change this, pass along DAGGER_BINARY=somewhere/dagger