Stefan Kolb
Stefan Kolb
This configuration works for me with the Ruby 2.0 v1.0.7 Puma AMI. https://gist.github.com/stefan-kolb/86aa8ad2b3c0973c8386 For v1.0.9 you need to delete the _add_bundle_exec_ task as this is done per default now.
Well, I think this is the code: https://github.com/stefan-kolb/paasyard/blob/master/provider/elasticbeanstalk/files/.ebextensions/eb.config But I bet they changed a lot over the time, so not sure if this still helps.
Expose nested namespace as standalone route does not work in swagger ui 2.1.4 and grape-swagger 0.20
I don't really know what is needed to reenable/fix this functionality as I didn't write it before. But I cannot see any nickname key inside this functionality or code, so...
Expose nested namespace as standalone route does not work in swagger ui 2.1.4 and grape-swagger 0.20
You should probably re-add the tests `api_with_standalone_namespace_spec.rb`, so you can debug whats going wrong here. As far as I know the tests were removed between the transition from 0.11 to...
This is conflicting with issue #6. Either allow multiple service types or be able to group per service type in the filter dropdown. Another possibility is to add all services...
Implement this for frameworks and middleware per runtime, first?!
Also consistency problems if different runtimes are set with current tests. Add `native` option? Does not handle middleware that only runs for selected other runtimes...
Maybe filter on infrastructure countries, too.
- [x] Base technologies - [ ] isolation.