| commit | 313816f41244d7520eb2b6f8c231328ee5b7a4ef | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Tue Dec 22 16:52:26 2020 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Tue Dec 22 16:52:26 2020 +0100 |
| tree | 7a8aa08b48b22a7843afd76c14b8fd2ebe3c2cfb | |
| parent | d9ed6560d5db2783252945e1dd3c2e4f908c019e [diff] |
Disable integrity and encryption for debug builds This disables disk encryption and integrity when running in the debug profile. It also makes mkfs.xfs not issue discards as the backend is either a sparse file (during development) or dm-crypt/dm-integrity which ignores them. In both cases they are counterproductive and slow things down. Test Plan: Not exercised by normal tests, manually tested. X-Origin-Diff: phab/D681 GitOrigin-RevId: 24fae1e3de8d852b414ebd50f3fbe032440683fb
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
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)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //metropolis/cli/dbg -- kubectl describe
This repository is compatible with the IntelliJ Bazel plugin. 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.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
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.
It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:
bazel run intellij/localconfig $(pwd)