Clever Geek Handbook

What is the advantage of creating a Sinatra / Rack application in a single, locally executable file?

I read the description in Vegas, which is a stone that

aims to solve the simple problem of creating executable versions of a Sinatra / Rack Application.

I didn't know it was a problem to be solved.

The reason this seems like a dubious benefit is because:

Now if you run ./my_app it should:

    * find an appropriate rack handler (thin. mongrel)
    * find an available port
    * launch the app in a browser
    * put itself in the background
    * write a .pid and a .url file

Isn't it too easy to launch the Sinatra app? You just type

ruby my_app.rb

and all the same things happen, except that the application is a background process.

Why do you need an executable file for this?

+2


source to share


1 answer


Sounds like a convenience wrapper around Sinatra / Rack to me, except for the demo ( .pid

and .url

will likely "find" it again) and launching the browser, it doesn't seem to have any advantage over naked Sinatra / Rack.



+2


source






More articles:


All Articles