mirror of
https://github.com/google/nomulus.git
synced 2025-05-22 04:09:46 +02:00
Remove empty section headers from Markdown docs
The section headers can be re-added later along with their actual content. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=136349771
This commit is contained in:
parent
f1ad34b12f
commit
00234a1038
4 changed files with 1 additions and 28 deletions
|
@ -425,9 +425,3 @@ placeholder for the App Engine app name:
|
||||||
temporary files from building up, a 90-day or 180-day lifecycle should be
|
temporary files from building up, a 90-day or 180-day lifecycle should be
|
||||||
applied to the bucket, depending on how long you want to be able to go back
|
applied to the bucket, depending on how long you want to be able to go back
|
||||||
and debug MapReduce problems.
|
and debug MapReduce problems.
|
||||||
|
|
||||||
## Commit logs
|
|
||||||
|
|
||||||
## Web.xml
|
|
||||||
|
|
||||||
## Cursors
|
|
||||||
|
|
|
@ -3,8 +3,6 @@
|
||||||
This document contains information on the overall structure of the code, and how
|
This document contains information on the overall structure of the code, and how
|
||||||
particularly important pieces of the system are implemented.
|
particularly important pieces of the system are implemented.
|
||||||
|
|
||||||
## Dagger dependency injection
|
|
||||||
|
|
||||||
## Bazel build system
|
## Bazel build system
|
||||||
|
|
||||||
[Bazel](https://www.bazel.io/) is used to build and test the Nomulus codebase.
|
[Bazel](https://www.bazel.io/) is used to build and test the Nomulus codebase.
|
||||||
|
@ -37,7 +35,7 @@ the dependencies or use the
|
||||||
[generate_workspace](https://github.com/bazelbuild/bazel/tree/master/src/tools/generate_workspace
|
[generate_workspace](https://github.com/bazelbuild/bazel/tree/master/src/tools/generate_workspace
|
||||||
tool to do it.
|
tool to do it.
|
||||||
|
|
||||||
### How to generate `EAR`/`WAR` archives for deployment
|
### Generating EAR/WAR archives for deployment
|
||||||
|
|
||||||
There are special build target types for generating `WAR` and `EAR` files for
|
There are special build target types for generating `WAR` and `EAR` files for
|
||||||
deploying Nomulus to GAE. These targets, `zip_file` and `registry_ear_file` respectively, are used in `java/google/registry/BUILD`. To generate archives suitable for deployment on GAE:
|
deploying Nomulus to GAE. These targets, `zip_file` and `registry_ear_file` respectively, are used in `java/google/registry/BUILD`. To generate archives suitable for deployment on GAE:
|
||||||
|
@ -54,10 +52,6 @@ bazel-genfiles/java/google/registry/registry_default.war
|
||||||
bazel-genfiles/java/google/registry/registry_tools.war
|
bazel-genfiles/java/google/registry/registry_tools.war
|
||||||
```
|
```
|
||||||
|
|
||||||
## Flows
|
|
||||||
|
|
||||||
## Commit logs and backups
|
|
||||||
|
|
||||||
## Cursors
|
## Cursors
|
||||||
|
|
||||||
Cursors are `DateTime` pointers used to ensure rolling transactional isolation
|
Cursors are `DateTime` pointers used to ensure rolling transactional isolation
|
||||||
|
@ -119,12 +113,6 @@ is of limited use -- the best you can do is to `@Inject` serializable fields on
|
||||||
the entire MapReduce `Action`, and then set them manually on the mapper/reducer
|
the entire MapReduce `Action`, and then set them manually on the mapper/reducer
|
||||||
classes in their constructor.
|
classes in their constructor.
|
||||||
|
|
||||||
## Actions and servlets
|
|
||||||
|
|
||||||
## Foreign key indexes
|
|
||||||
|
|
||||||
## Point-in-time accuracy
|
|
||||||
|
|
||||||
## Guava
|
## Guava
|
||||||
|
|
||||||
The Nomulus codebase makes extensive use of the
|
The Nomulus codebase makes extensive use of the
|
||||||
|
@ -168,8 +156,6 @@ type objects are immutable and have sane default implementations of `toString`,
|
||||||
`hashCode`, and `equals`. They are often used as parameters and return values to
|
`hashCode`, and `equals`. They are often used as parameters and return values to
|
||||||
encapsulate related values together.
|
encapsulate related values together.
|
||||||
|
|
||||||
## EPP resource hierarchy
|
|
||||||
|
|
||||||
## Poll messages
|
## Poll messages
|
||||||
|
|
||||||
Poll messages are the mechanism by which EPP handles asynchronous communication
|
Poll messages are the mechanism by which EPP handles asynchronous communication
|
||||||
|
@ -199,5 +185,3 @@ messages that extend it:
|
||||||
|
|
||||||
Queries for poll messages by the registrar are handled in `PollRequestFlow`, and
|
Queries for poll messages by the registrar are handled in `PollRequestFlow`, and
|
||||||
poll messages are ACKed (and thus deleted) in `PollAckFlow`.
|
poll messages are ACKed (and thus deleted) in `PollAckFlow`.
|
||||||
|
|
||||||
## Security
|
|
||||||
|
|
|
@ -1,3 +0,0 @@
|
||||||
# Extension points
|
|
||||||
|
|
||||||
The various places the system can be extended by plugging in additional code.
|
|
|
@ -3,8 +3,6 @@
|
||||||
This document covers procedures that are typically used when running a
|
This document covers procedures that are typically used when running a
|
||||||
production registry system.
|
production registry system.
|
||||||
|
|
||||||
## OT&E onboarding
|
|
||||||
|
|
||||||
## Stackdriver monitoring
|
## Stackdriver monitoring
|
||||||
|
|
||||||
[Stackdriver Monitoring](https://cloud.google.com/monitoring/docs/) is used to
|
[Stackdriver Monitoring](https://cloud.google.com/monitoring/docs/) is used to
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue