We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How should developing and running our services be documented? Centralized docs? Mainly centralized docs with final parts in their home repos (a la https://github.com/geneontology/devops-documentation/)? Repo/service-specific doc (a la https://github.com/geneontology/go-fastapi/blob/main/provision/production/PRODUCTION_PROVISION_README.md)?
We'll need to select an overall strategy and have a plan for moving to it.
The text was updated successfully, but these errors were encountered:
basic file let us say this is for #2
446dbe9
Update README.md
96c79c7
Update with what I think the current state is (#2)
pkalita-lbl
No branches or pull requests
How should developing and running our services be documented? Centralized docs? Mainly centralized docs with final parts in their home repos (a la https://github.com/geneontology/devops-documentation/)? Repo/service-specific doc (a la https://github.com/geneontology/go-fastapi/blob/main/provision/production/PRODUCTION_PROVISION_README.md)?
We'll need to select an overall strategy and have a plan for moving to it.
The text was updated successfully, but these errors were encountered: