-
Notifications
You must be signed in to change notification settings - Fork 1
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
MB-9804 update local setup and instructions #78
MB-9804 update local setup and instructions #78
Conversation
…ASDF support Also clean up a few commands
Removed `ASDF` docs entirely because it relied on how the old `Markdown` file worked. Left `docker` setup, but marked as unsupported.
It's needed for the test utils from `locust`. Unfortunately `locust` is still using a deprecated way (`tests_require`) of defining their requirements for tests, which means we can't import them more easily (e.g. by listing it as `locust[test]` or something. Maybe in a future version we'll be able to do that rather than listing an individual requirement.
This makes my heart sing! I'll give it a try in a bit. |
|
I think we need to say something about adding |
Also, I use the fish shell and the command that was added to my config doesn't work in fish:
Looking at the node setup, I think this is what is needed for fish:
|
Okay, so after I modified the last 2 lines in my fish config to this:
and after opening a new terminal tab, I was finally able to run |
Thanks for the review @monfresh! I've made those edits and will see about finding another fish user to test with. |
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.
Both the nix and pyenv instructions LGTM!
README.md
Outdated
* [MilMove/Office domains](#milmoveoffice-domains) | ||
* [Handling Rate Limiting](#handling-rate-limiting) | ||
* [Metrics](#metrics) | ||
* [References](#references) | ||
|
||
<!-- Added by: ronak, at: Wed Oct 20 10:24:39 EDT 2021 --> |
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 see that this line hasn't been modified. Is there a standardized way of updating the TOC? I have been running
./gh-md-toc --insert README.md
Maybe we need more documentation around this/add some more instructions in the comments?
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.
Ah my bad, I missed that line. Yeah, I thought about adding that to the docs, or even adding a script or Makefile target that does it for us so we don't have to remember to do it the same way each time. i can add it since I'm already editing several things related to setup
.gitignore
Outdated
Brewfile | ||
pour.sh | ||
Brewfile.local.lock.json | ||
Brewfile.lock.json |
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.
Nit: There are 5 files that end without new line characters
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 can add a .editorconfig
file to make sure we're more consistent
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.
Oh wait, we already have one. Weird, idk why it didn't auto-fix these for me. Maybe I have it turned off in my editor for some reason.
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.
Oh haha, just barely looked at it more closely. We actually haven't set it to insert final newlines. I'll update it.
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.
LGTM. Left a comment about spacing in the TOC if you want to look into it
@@ -131,6 +60,10 @@ pretty: ensure_venv ## Prettify the code | |||
lint: ensure_venv ## Run linting tests | |||
flake8 . | |||
|
|||
.PHONY: generate_readme_toc | |||
generate_readme_toc: ## Re-generates and re-places the table of contents for the README.md | |||
./gh-md-toc --insert README.md |
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.
Thanks for adding this and adding the package as part of the install script!
README.md
Outdated
* [Base Installation](#base-installation) | ||
* [Setup: Pyenv](#setup-pyenv) | ||
* [Setup: Nix](#setup-nix) | ||
* [Installing Python Dependencies and Pre-commit Hooks](#installing-python-dependencies-and-pre-commit-hooks) | ||
* [Unsupported Setup](#unsupported-setup) | ||
* [Alternative Setup: Docker](#alternative-setup-docker) |
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 just realized that it is using 3 spaces for each indent level for some reason. I just did a cursory look and it seems like it should honor your editor settings (ref).
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 tried fixing it, but it keeps generating with the 3 spaces. I thought it maybe was detecting a difference in spaces, but even after making the whole file follow 2 spaces (even tried with making the python do this, but didn't commit that in the end), and it still does 3 spaces. Very weird. I think we use a different tool on mymove, so maybe we can use that instead. Though that should be a future pr.
Trying to fix some bad spacing and test if gh-md-toc can actually honor our spacing or not.
Also add link to docs in case anyone else needs to edit it
Description
We want to make it easier for people to set up the project locally. To that end, I've implemented fresh-brew since we're testing it out in a few repos and it makes it much faster and easier to get going.
We also want to make this repo easier to maintain so we're dropping support for
asdf
anddocker
local setups in favor ofpyenv
andnix
. This PR removes ASDF entirely because it was too intertwined with howpyenv
worked. Thedocker
instructions are still available, but are marked as unsupported.Reviewer Notes
Should we just fully remove
docker
local setup? Like the instructions andMakefile
commands?Setup
Try out the setup steps outlined in the README and let me know if you have any issues.
Code Review Verification Steps
References