You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the new pipenv workflow, the command to start a grow devserver is pipenv run grow run. This would be slightly cleaner if grow was an alias for grow run (command would be something like pipenv run grow --port=8080
The text was updated successfully, but these errors were encountered:
I think I figured out a way to make grow be the same as grow run, but the method that I tried didn't accept the arguments or flags since they are not configured for the main grow command group. So really you would be able to run grow run, but nothing else which might make it a bit pointless.
Wondering what other similar projects do as their default. It can be nice
to get a help command as a default, but I agree pipenv run grow has a good
ring to it.
On Fri, Jun 12, 2020, 9:23 PM Randy Merrill ***@***.***> wrote:
I think I figured out a way to make grow be the same as grow run, but the
method that I tried didn't accept the arguments or flags since they are not
configured for the main grow command group. So really you would be able
to run grow run, but nothing else which might make it a bit pointless.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1098 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE527KPYZMY7I6EGEHC33TRWL5N5ANCNFSM4N4YD5KA>
.
With the new
pipenv
workflow, the command to start a grow devserver ispipenv run grow run
. This would be slightly cleaner ifgrow
was an alias forgrow run
(command would be something likepipenv run grow --port=8080
The text was updated successfully, but these errors were encountered: