| commit | ac43b3edac4df7964cbe349f8e39f6346871ea3d | [log] [tgz] |
|---|---|---|
| author | q3k <q3k@hackerspace.pl> | Sun Apr 12 12:38:48 2020 +0000 |
| committer | Gerrit Code Review <gerrit@hackerspace.pl> | Sun Apr 12 12:38:48 2020 +0000 |
| tree | 2ed4c863911c49c0e252af646429400abd1b5efb | |
| parent | adb72ccdec49b4fbf4483a02983644e47ee702d9 [diff] | |
| parent | ebaa40894d9482e941d073efff01091d64892f47 [diff] |
Merge "devtools/depotview: fix stale branches, clone bug"
- app/
- bgpwtf/
- bzl/
- cluster/
- dc/
- devtools/
- doc/
- gcp/
- go/
- hswaw/
- kube/
- personal/
- third_party/
- tools/
- .bazelrc
- .gitignore
- BUILD
- COPYING
- env.fish
- env.sh
- hackdoc.toml
- README.md
- WORKSPACE
hscloud is the main monorepo of the Warsaw Hackerspace infrastructure code.
Any time you see a //path/like/this, it refers to the root of hscloud, ie. the path path/like/this in this repository. Perforce and/or Bazel users should feel right at home.
Viewing this documentation
For a pleaseant web viewing experience, see this documentation in hackdoc. This will allow you to read this markdown file (and others) in a pretty, linkable view.
Getting started
You will need Bash and Bazel (1.2.0+).
First, clone the repository:
git clone https://gerrit.hackerspace.pl/hscloud cd hscloud
Then, set up everything:
. ./env.sh # setup PATH and hscloud_root tools/install.sh # build tools
A bunch of common tools will appearify in your $PATH. You should now be ready to follow other documentation.
This does not pollute your system, and you can work on multiple hscloud checkouts independently.
What now?
If you want to use our Kubernetes cluster to run some stuff, see //cluster/doc/user.md.
If you're looking for administrative docs about cluster maintenance, see //cluster/doc/admin.md.
If you want to browse the source of hscloud in a web browser, use gerrit's gitiles.
If you want to learn how to contribute to this repository, see //doc/codelab/gerrit.
If you want help, talk to q3k, informatic or your therapist.