mirror of
https://github.com/google/nomulus.git
synced 2025-08-12 12:39:39 +02:00
Add information to doc on which app the nomulus tool connects to
------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=137998955
This commit is contained in:
parent
dcd7f6e1e7
commit
050e734f6f
1 changed files with 10 additions and 0 deletions
|
@ -9,6 +9,16 @@ recent export failed. Its code lives inside the tools package
|
||||||
(`java/google/registry/tools`), and is compiled by building the `nomulus` target
|
(`java/google/registry/tools`), and is compiled by building the `nomulus` target
|
||||||
in the Bazel BUILD file in that package.
|
in the Bazel BUILD file in that package.
|
||||||
|
|
||||||
|
The tool connects to the Google Cloud Platform project (identified by project
|
||||||
|
ID) that was configured in your implementation of `RegistryConfig` when the tool
|
||||||
|
was built. See the [configuration guide](./configuration.md) for more
|
||||||
|
information. The tool can switch between project IDs that represent different
|
||||||
|
environments within a single overall platform (i.e. the production environment
|
||||||
|
plus development and testing environments); see the `-e` parameter below. For
|
||||||
|
example, if the platform is called "acme-registry", then the production project
|
||||||
|
ID is also "acme-registry", and the project ID for the sandbox environment is
|
||||||
|
"acme-registry-sandbox".
|
||||||
|
|
||||||
## Build the tool
|
## Build the tool
|
||||||
|
|
||||||
To build the `nomulus` tool, execute the following `bazel build` command inside
|
To build the `nomulus` tool, execute the following `bazel build` command inside
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue