| commit | 7a510198b10c0b78f87c74a76e429097a757373d | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Mon Jul 04 15:31:38 2022 +0000 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Tue Jul 05 11:33:43 2022 +0000 |
| tree | 3f5acc9f346b977de524017ae61346811ec24ddd | |
| parent | adb98f9d02a0b2c6b5def344d421a79ab9c6b37e [diff] |
m/c/metroctl: embed installer and add argument for bundle This embeds the installer in metroctl for easier distribution and adds an option for passing a bundle path explicitly. For the MVP this allows users to download metroctl and a bundle separately and make an installer out of them. Change-Id: I00f481c30a2e843d336248aad0dc4030d03c4576 Reviewed-on: https://review.monogon.dev/c/monogon/+/821 Tested-by: Jenkins CI Reviewed-by: Mateusz Zalega <mateusz@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 -c dbg
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -c dbg -- kubectl describe
Run tests:
scripts/bin/bazel test -c dbg //...