| commit | b6c0aa9703d7b92ea0a94f16a81a7218fc80d36b | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Thu Feb 24 17:53:40 2022 +0100 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Tue Mar 08 12:26:08 2022 +0000 |
| tree | fde7cf7668a12c10d903576adc591d8d33b62412 | |
| parent | 942f5e2188f67d78fe8da86f42e1902427792f2b [diff] |
metropolis: use microcode This ties together all previous work and actually makes the installer and OS use microcode via the early microcode loader. Change-Id: I4e3214c30e4eff1d231d462fceddd2e353d28731 Reviewed-on: https://review.monogon.dev/c/monogon/+/549 Reviewed-by: Sergiusz Bazanski <serge@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 //...