| commit | 4b613303b18ddd5d536b9c8b2aa26b0f80ffb803 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <q3k@hackerspace.pl> | Sat Feb 13 13:16:10 2021 +0100 |
| committer | Serge Bazanski <q3k@hackerspace.pl> | Mon Feb 15 22:11:35 2021 +0100 |
| tree | 02224b26e08353b9d8cf5d2b44eee79919e8739f | |
| parent | 55cc9ab1779df9c9cbd7b86825ae44b54f3768aa [diff] |
RFC: *: move away from rules_nixpkgs This is an attempt to see how well we do without rules_nixpkgs. rules_nixpkgs has the following problems: - complicates our build system significantly (generated external repository indirection for picking local/nix python and go) - creates builds that cannot run on production (as they are tainted by /nix/store libraries) - is not a full solution to the bazel hermeticity problem anyway, and we'll have to tackle that some other way (eg. by introducing proper C++ cross-compilation toolchains and building everything from C, including Python and Go) Instead of rules_nixpkgs, we ship a shell.nix file, so NixOS users can just: jane@hacker:~/hscloud $ nix-shell hscloud-build-chrootenv:jane@hacker:~/hscloud$ prodaccess This shell.nix is in a way nicer, as it immediately gives you all tools needed to access production straight away. Change-Id: Ieceb5ae0fb4d32e87301e5c99416379cedc900c5
- WORKSPACE[diff]
- cluster/tools/BUILD[diff]
- third_party/nix/BUILD[Deleted - diff]
- third_party/nix/python.nix[Deleted - diff]
- third_party/nix/repository_rules.bzl[Deleted - diff]
- app/
- bgpwtf/
- bzl/
- cluster/
- dc/
- devtools/
- doc/
- games/
- gcp/
- go/
- hswaw/
- kube/
- nix/
- ops/
- personal/
- third_party/
- tools/
- .bazelrc
- .gitignore
- BUILD
- ci_presubmit.sh
- COPYING
- default.nix
- env.fish
- env.sh
- hackdoc.toml
- OWNERS
- 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
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.
Directory Structure
Directories you should care about:
- app: external services that we host that are somewhat universal: matrix, covid-formity, etc.
- bgpwtf: code related to our little ISP
- cluster: code related to our Kubernetes cluster (
k0.hswaw.net) - dc: code related to datacenter automation
- devtools: code related to developer tooling, like gerrit or hackdoc
- doc: high-level documentation that doesn't fit anywhere else, ie. codelabs
- hswaw: Warsaw Hackerspace specific/internal services. The line between this and app is unfortunately blurry.
- personal: user's personal (experimental) directories
- kube, go: code specific to languages but general to the whole of hscloud
Licensing
Unless noted otherwise, code in hscloud is licensed under the BSD 0-clause license - see COPYING.