-
Notifications
You must be signed in to change notification settings - Fork 63
Automate PATH verification in install_prerequisites.sh, simplify README
#858
New issue
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
Conversation
| $ ./tools/install_prerequisites.sh | ||
| ---- | ||
|
|
||
| Alternatively, the manual installation steps as follows: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I admit I'm a little sad to see this section go. I feel like this is useful documentation for the important third-party pieces that we're using. At the same time, it probably doesn't make sense to have both this and an automated version that can get out of sync. I wonder if there's a useful compromise -- what if we move more of this documentation into install_prerequisites.sh itself? Things I could imagine noting in that script:
- That Diesel uses the native libpq to talk to to PostgreSQL (CockroachDB in our case)
- That the test suite expects the
cockroachandclickhousecommands on your PATH - That the brand/omicron1/tools package is used for deploying control plane components into zones on a test machine [as opposed to a local build or test suite run]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good suggestion, I've added much more documentation to the script itself.
Automating as much of the README as possible within the installation script to simplify the onboarding process.