Web application in Ruby. Where to start?


Warning: count(): Parameter must be an array or an object that implements Countable in /home/styllloz/public_html/qa-theme/donut-theme/qa-donut-layer.php on line 274
0 like 0 dislike
5 views
Then decided to port one of the PHP app to Ruby. Not so much with the goal to port for practical use, how to obtain experience. First started doing as a CGI app, debugging in the console. Then I wanted to see in the browser, I saw, I wanted to test the speed — I was horrified. Decided to look for options. Here's what I found:

1. TCPServer — somehow does not inspire

2. Various web server modules for Apache/nginx is understood that no particular difference

3. Rack — for him and there is no difference :) as I understand the analogue of WSGI in Python

4. Sinatra — like all simply and immediately tell what is missing, like WebOb first sight or like a naked PHP :) Written and immediately realized what is missing — working with forms and bind them to the database

5. RoR — as-all strongly encapsulated, I think for the first little fit, it's like starting to learn PHP with symfony or Yii. Like going, what's under the hood going on...


Here I stand at a crossroads of how to proceed. 1 and 2, there is no — raw HTTP processing is not desirable. A toss-up between Rack and Synatra. Or all Rails? :-/ What's more will learn to solve a variety of real problems, but at the same time without creating artificial? Maybe even a option?
by | 5 views

4 Answers

0 like 0 dislike
You have answered your own question.
You essentially have a choice between 3, 4 and 5
4 — immediately raised two red 5 — from Oracle unsuitable for use as a... discover What option is left?
by
0 like 0 dislike
>Sinatra — like all simply and immediately tell what is missing, like WebOb first sight or like a naked PHP
> type bare PHP
/0
\r
Start with Sinatra, deal in ruby, switch to RoR.
\r
Still have a Padrino and Grape, the first is Sinatra with whistles perdelkami, the second the same, but to create a RESTful API
by
0 like 0 dislike
Substitution of concepts detected.
\r
Rack is the interface between the web server and web framework. The de-facto standard. Without it anywhere.
Passenger module for apache/nginx to run Rack.
Thin, Ebb,... web servers, does not require apache/nginx.
Sinatra/Padrino/Rango/RoR/... — web-framework.
\r
I would start with Sinatra + Thin.
Then you can connect to the Siantra Padrino (the functionality is practically the Rails, but much more modular and human), and gradually to it to go at all.
\r
RoR still need to know.
\r
For production use of different options. At current I have nginx+Passenger+RoR.
\r
It is also worth studying:
— DataMapper/ActiveRecord/Sequel to link to the database;
— The HAML/Erb templates;
— Compass/SASS for CSS templates.
\r
Good luck!
by
0 like 0 dislike
You just do not understand the beauty Sinatra. It is a framework which does not impose you a selection of the ORM and templating engine. He doesn't even force you to use MVC pattern (But you can use it). Here's a good example application in Sinatra.
\r
Also I can advise to look at the framework Padrino. As written on their website, is "The Elegant Ruby Web Framework". And it's true. Padrino, and Sinatra doesn't impose any libraries you are using. So you can choose the ORM, the templating engine for html and css database type (supported, not only relational databases) and the library for testing. While Padrino has generators in Rails style and compared to Sinatra greatly reduces routine.
by

Related questions

0 like 0 dislike
7 answers
0 like 0 dislike
4 answers
asked Apr 24, 2019 by webninja_surgut
0 like 0 dislike
1 answer
asked Apr 11, 2019 by webninja_surgut
0 like 0 dislike
1 answer
0 like 0 dislike
3 answers
110,608 questions
257,186 answers
0 comments
27,943 users