| commit | a4edfa9e12ce6db3216da01be7bf35825893c749 | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Sun Dec 13 18:55:21 2020 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Sun Dec 13 18:55:21 2020 +0100 |
| tree | 387c7d4d0f0499609ac03fea2c68afda5aa862be | |
| parent | dbac6ccbf5325aa737280ac79b3cc5916e9b57f6 [diff] |
Fix IntelliJ instructions in README We probably need more in-depth instructions for the open source project, but the existing ones should at least be correct. Test Plan: N/A X-Origin-Diff: phab/D660 GitOrigin-RevId: 5e9dd3379c17a23539651624dfc64daafd156b28
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 //core/cmd/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.