Clarify dev
vs server
in command descriptions
#144
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's hard to condense the distinction down to just a handful of words, so feel free to tweak.
I also wonder if we should combine the commands somehow, since the distinction here between
dev
andserver
isn't intuitive, though I understand how they came to be, of course.Maybe just
hanami dev
does the following:Procfile.dev
exist?web: bundle exec hanami server
?And then add a flag like
hanami dev --ruby
to just start Rack::Server if that's needed