commit | 7fe415c31faeecab08d18785eecd7d0e18ece08b | [log] [tgz] |
---|---|---|
author | radex <radex@hackerspace.pl> | Sat May 03 15:50:02 2025 +0200 |
committer | radex <radex@hackerspace.pl> | Sat May 03 13:51:20 2025 +0000 |
tree | 2cff05bd728f5e21e058bb3c3f29a4516871d981 | |
parent | 62487213c149dd534d1716a934aa8460dc48aed8 [diff] |
k1/calico: fix BGP config - fix k1 to use 65004 AS number (65003 is reserved for k0). - announce k1 service addresses so that they're reachable from k0 Change-Id: I18bd1270b102e7c361e0d211b0e75b2bef4db3c0 Reviewed-on: https://gerrit.hackerspace.pl/c/hscloud/+/2440 Reviewed-by: q3k <q3k@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.
Initial setup: //doc/codelabs/getting-started/bazel-go.md
Initial bazel build for tools: bazelisk run //tools:install
For additional documentation go to //cluster
hscloud supports simpler setup and working with its source via dev containers. After opening the hscloud directory in VSCode, you should see a notification in the bottom right corner with suggested extensions. Currently the only suggested extension is the Dev Containers extension which allows you for one-click build of hscloud repository, without having to figure out all of its dependencies.
After building the container you should be able to create a new terminal from the vscode instance. It will be connected to the docker image which already has all the necessary tools built and included into your environment/PATH.
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.