commit | 0f8e5a21324d10590e7a015bf4946f7c857f87b5 | [log] [tgz] |
---|---|---|
author | Serge Bazanski <q3k@hackerspace.pl> | Sat Oct 16 20:53:51 2021 +0000 |
committer | q3k <q3k@hackerspace.pl> | Sun Oct 17 21:21:58 2021 +0000 |
tree | 2e29e3ece57e196a0a58b32ec8726de004b743b9 | |
parent | 20c6bcb7305d4b85c5fd6dfc72c04c68b772d15f [diff] |
*: do not require env.sh This removes the need to source env.{sh,fish} when working with hscloud. This is done by: 1. Implementing a Go library to reliably detect the location of the active hscloud checkout. That in turn is enabled by BUILD_WORKSPACE_DIRECTORY being now a thing in Bazel. 2. Creating a tool `hscloud`, with a command `hscloud workspace` that returns the workspace path. 3. Wrapping this tool to be accessible from Python and Bash. 4. Bumping all users of hscloud_root to use either the Go library or one of the two implemented wrappers. We also drive-by replace tools/install.sh to be a proper sh_binary, and make it yell at people if it isn't being ran as `bazel run //tools:install`. Finally, we also drive-by delete cluster/tools/nixops.sh which was never used. Change-Id: I7873714319bfc38bbb930b05baa605c5aa36470a Reviewed-on: https://gerrit.hackerspace.pl/c/hscloud/+/1169 Reviewed-by: informatic <informatic@hackerspace.pl>
hscloud
is the main monorepo of the Warsaw Hackerspace infrastructure code.
See //doc/codelabs for tutorials on how to use hscloud.
If you want to browse the source of hscloud
in a web browser, use cs.hackerspace.pl.
If you want some other help, talk to q3k, informatic or your therapist.
Directories you should care about:
k0.hswaw.net
)Unless noted otherwise, code in hscloud is licensed under the BSD 0-clause license - see COPYING.