ruby-grape / ruby-grape/grape-swagger
changes to default web server broke my build
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.1k
- Forks
- 479
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 6
Description
Hi,
A repo I'm working on was working perfectly until the recent update from grape-swagger 1.4.2 to 1.5 where I started getting rackup errors .
.asdf/installs/ruby/3.1.2/lib/ruby/gems/3.1.0/gems/bundler-2.3.20/lib/bundler/rubygems_integration.rb:308:in `block in replace_bin_path': can't find executable rackup for gem rack (Gem::Exception)
I managed to track it down to this change https://github.com/ruby-grape/grape-swagger/pull/853, my repo already has puma gem installed and configured but now with this change I have to pass in extra params to rackup to define which server to use rackup --server puma.
It might be worth documenting this change a bit more in the update path doc.
Is there a better way to allow developers to perhaps exclude Webrick when setting up grape-swagger?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the update path documentation and the grape-swagger 1.4.2-to-1.5 change linked in PR #853; reproduce the rackup failure described with Ruby 3.1.2 and the existing Puma setup. Done means the update guidance clearly explains the web-server change and any supported way to avoid or configure Webrick.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100