improve failure handling in `start' command #242

Merged
Bogdanp merged 2 commits from master into master 3 years ago
Bogdanp commented 3 years ago (Migrated from github.com)

I was playing around with pollen today and I saw that the start command failed to notice that my server didn't start up properly because I already had a server running on 8080. I fixed that in the first commit and then I had some trouble figuring out how to tell it to use a different port, because raco pollen start --help made no mention of the positional port argument so the 2nd commit addresses that issue.

I was playing around with pollen today and I saw that the start command failed to notice that my server didn't start up properly because I already had a server running on 8080. I fixed that in the first commit and then I had some trouble figuring out how to tell it to use a different port, because `raco pollen start --help` made no mention of the positional `port` argument so the 2nd commit addresses that issue.
mbutterick commented 3 years ago (Migrated from github.com)

Thanks! The docs are sketchy on the use of confirmation-channel — I never understood how to use it.

Thanks! The docs are sketchy on the use of `confirmation-channel` — I never understood how to use it.
The pull request has been merged as c02eab7b90.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b master master
git pull origin master

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff master
git push origin master
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mbutterick/pollen#242
Loading…
There is no content yet.