-
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
Improve first-time setup workflow #42
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The first-time setup workflow as of initial public release is effectively:
make deps
, which will error if Homebrew isn't found.make install-homebrew
to install Homebrew, then runmake deps
againmake deps
, viadeps-brew
will install deps from Homebrew including pyenvmake deps
, viainstall-python
viadeps-py
, will install Python from pyenv, which will error ifpyenv
isn't foundpyenv
loading code to shell rcfile, then runmake deps
againmake deps
, viainstall-poetry
viadeps-py
, will install Poetry using pyenv-installed Python or system Python, whichever it detects first, and only ifpoetry
isn't available as of the start of the current run ofmake
.make deps
, viapoetry-install
viadeps-py
, will install Python deps using Poetry, which will error ifpoetry
isn't found~/.local/bin
, Poetry's default installation path, to their PATH in shell rcfile, then runmake deps
again.There are some steps I skipped in here related to telling Poetry which Python to use (it generally just works) and sync'ing Peru (also generally just works).
These one-time setup steps ("user must manually…") are annoying. While some tasks tell the user that they need to read command output, too many users just… don't.
Possible solutions:
README.md
or at the end ofmake deps
.make wreck-my-rcfile
or maybe more nicelymake setup-rcfile-once
that modifies the shellrc with what should be put there carefully manually.The text was updated successfully, but these errors were encountered: