| commit | 05c1db9d0f608b793cee96e8f947534d682c3694 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Thu Jun 23 14:24:29 2022 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Fri Jun 24 13:11:47 2022 +0000 |
| tree | b0681c760d1bf825d54d4393207e412ca93800d7 | |
| parent | 1fbc5975a74174c3719ae2a15b60d202b6b4e609 [diff] |
m/n/c/rpc: remove leftover ClusterServices These were mostly used back when the Curator leader/follower had per-method dispatching. We don't do that anymore. Change-Id: I202254e4deabfb3dc150d69a28156d8824009032 Reviewed-on: https://review.monogon.dev/c/monogon/+/794 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 //...