CLI Support for rackup or config.ru Rack application?

[boazsegev]

HI,

I was wondering if there's any way to run Rack applications from the command line interface (CLI)?

The default Rack application file is config.ru and it might contain anything from a Rails application to a simple Hello World (example config.ru file):

out = [200, {"Content-Length" => "12"}, ["Welcome Home"] ].freeze
app = Proc.new { out }
run app

These can be executed using the rackup command using Puma, iodine, Thin, etc' by adding the -s flag.

Could agoo be added to this?

I'd love to be able to run Rails, Sinatra or any other application using:

$ rackup -s agoo

The downside is that rackup sometimes automatically adds middleware to the application (in development mode), so I'd be slightly happier if the CLI itself could run the config.ru app... This way, the Rack application could be executed without any surprises when agoo is called in the same folder as the app. i.e.:

$ agoo -p 3000

I know this will break backwards compatibility for the CLI, but using rackup should be possible without breaking backwards compatibility, shouldn't it?

[ohler55]

rackup -S agoo should work right now but since rack does not name agoo in the like require agoo is needed to allow that.

[boazsegev]

I tried rackup -p 3000 -s agoo -r agoo which failed.

Using a capital -S doesn't seem to solve it (I get "invalid option").

iodine works with rackup...

Perhaps it has to do with this folder structure or this line... I can't remember what finally worked, but something did, I think maybe both were required.

[boazsegev]

I got it to work with a capital A in Agoo...

$ RACK_ENV=production rackup -p 3000 -r agoo -s Agoo

IMHO, CLI integration could be improved, but the important part is that I got it running.

Thanks!

[ohler55]

I need more feedback to improve. Your feedback helps. Am typing from a phone so the -s was autocorrected. I remember now about capital A in Agoo. Rack expected that as the case sensitive module or class name.

[boazsegev]

Rack expected that as the case sensitive module or class name.

Maybe register two names ;-)

[ohler55]

Maybe. Pretty ugly work around.

…

On Mar 25, 2018, at 17:42, Bo ***@***.***> wrote: Rack expected that as the case sensitive module or class name. Maybe register two names ;-) — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[boazsegev]

This might help:

::Rack::Handler.register('agoo', 'Rack::Handler::Agoo') if defined?(::Rack::Handler)

[ohler55]

Thanks. I think I was doing it the hard way.

…

On Mar 25, 2018, at 18:29, Bo ***@***.***> wrote: This might help: ::Rack::Handler.register('agoo', 'Rack::Handler::Agoo') if defined?(::Rack::Handler) — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[ohler55]

The 1.2.2 release should allow lower case agoo to be used.

[ohler55]

All working. Closing.