| commit | 8f72b5ddae45109331258cea8af0662a608c1123 | [log] [tgz] |
|---|---|---|
| author | Mateusz Zalega <mateusz@monogon.tech> | Fri Dec 03 17:08:59 2021 +0100 |
| committer | Mateusz Zalega <mateusz@monogon.tech> | Tue Dec 07 12:13:07 2021 +0000 |
| tree | 00525a79ad1d4a0baa8e59a5aebae7767a5616d7 | |
| parent | 02d69e99f0c8ccdd9f53e5bc6c2a5e4ee26cbd83 [diff] |
coding style: fix error strings The way errors are passed to log was changed according to [1]. [1] https://github.com/golang/go/wiki/CodeReviewComments#error-strings Change-Id: I75194557d4f3b2f9f5e286a40fe4f0a4648eb71f Reviewed-on: https://review.monogon.dev/c/monogon/+/458 Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
This is the main repository containing the source code for the Monogon Project.
This is pre-release software - feel free to look around, and check back later for our first release!
Our build environment requires a working Podman binary (your distribution should have one).
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. All commands run inside the container, and necessary paths are mapped into the container.
The following steps are necessary:
Install Google's Bazel plugin in IntelliJ. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
Add the absolute path to your ~/.cache/bazel-monogon folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
Launch the node:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...