Is this still actively maintained?

[IotaSpencer]

I'm writing a gem that has to use a mini web framework to load up a git webhook receiver, I've tried a few other frameworks, namely

• Sinatra
  • Hangs on install so it can't be used in a docker container, which a prime user of my gem wants to do.
  • Is a bit more heavy than I want it to be
• NYNY
  • Doesn't hang on install, but constantly is giving me errors about a mismatched superclass and I can't seem to find the problem. And frustrates me with its lacking features.

But I also want to know if I'm able use App.run! in a Thor command instead of a config.ru so that the server can be started in a thread and stopped with a 'quit' command (which I have implemented in previous versions of the gem)

And also I want to know if i can easily change the bind host and bind port of the server, as I had set up a class method on my sinatra version to set the host and port, and NYNY only allows port, and not as nicely.

[Wardrop]

Hey @IotaSpencer, yeah I'm still maintaining Scorched. I'm using it for a number of personal projects of mine, and at the moment is doing everything I need it to do, though I'm happy to make changes/improvements/fixes for other people as they raise them, assuming those changes are consistent with the goals of Scorched and the problems it's aimed at solving.

I haven't personally used Thor or Docker, but it sounds like it might help to get yourself a little more familiar with Rack. Scorched is a relatively thin layer on top of the Rack library/gem.

I'm not sure how familiar you are with Rack, but to clarify, Rack is a specification for allowing web servers and ruby applications to talk to each other in a standardized manner. It defines a standard format (array) for requests to an application, and responses from an application. The Rack library (i.e. the 'rack' gem) on the other hand is intended to provide a lot of the boiler plate for handling those requests and responses, and actually working with HTTP requests, HTTP responses, cookies, headers, etc. It saves every web framework from having to re-invent the wheel.

App.run! is part of the Rack gem, so you might need to peel the covers back on it to see how it's initializing the server.

Of course give Scorched a go. I'd be curious to know if it works for you, and if it doesn't, what problems you're running into.