Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Clearly define best practices configuration for harvest/registry-mgr #217

Closed
jordanpadams opened this issue Dec 7, 2021 · 1 comment
Closed

Clearly define best practices configuration for harvest/registry-mgr #217

jordanpadams opened this issue Dec 7, 2021 · 1 comment
Assignees
@tdddblog @tloubrieu-jpl
Labels
B12.1 skip-i&t
Milestone
18.Jackie.Joyner-...

Comments

@jordanpadams
Copy link
Member

馃挕 Description

As noted by node comments, not clear from documentation what the ideal operational config should be.

  • Should I configure the details?
  • Should I not configure anything?
  • What is ideal?
@jordanpadams jordanpadams added this to the 18.Jackie.Joyner-Kersee milestone Dec 7, 2021
@jordanpadams jordanpadams changed the title Clearly define ideal, operational configuration for harvest/registry-mgr Clearly define best practices configuration for harvest/registry-mgr Dec 7, 2021
@jordanpadams
Copy link
Member Author

resolved per 4c19e8b

jordanpadams added a commit that referenced this issue Dec 10, 2021
@jordanpadams
Update config for improved quick start refs #217
03a2566
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tdddblog tdddblog

@tloubrieu-jpl tloubrieu-jpl

Labels
B12.1 skip-i&t
Projects
None yet
Milestone
18.Jackie.Joyner-Kersee
Development

No branches or pull requests
3 participants
@tdddblog @jordanpadams @tloubrieu-jpl