StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12134180
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-26T21:47:56.640
FavoriteCount
0
LastActivityDate
2012-08-26T22:47:23.820
LastEditDate
2012-08-26T22:47:23.820
LastEditorUserId
598057
OwnerUserId
598057
ParentId
12125924
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
I did my own exploration of this question and I think I found a solution which will allow me having one web-server running all my tiny apps at once. It is based on RackStack not-yet-a-gem created by Remi Taylor (@remi on Github) <a href="https://github.com/remi/rack-stack">https://github.com/remi/rack-stack</a>. RackStack is inspired by Rack::Builder, which as well seems being good for accomplishing a task like this - RackStack just goes in the same direction further, abstracting "stack" functionality in a way I found very nice and handy. Here is a demonstration of RackStack which consists of two sample apps (Sinatra and Rack): <a href="https://github.com/stanislaw/skeletons/tree/master/rack_stack">https://github.com/stanislaw/skeletons/tree/master/rack_stack</a>. To mimic stack app behavior on a real server I modified my /etc/hosts file to have localhost2 host pointing to 127.0.0.1. I fire up Thin server and then run requests on localhost or localhost2: the requests to 'localhost' are served by FirstApp, to 'localhost2' by SecondApp. I can't now foresee any problems that can appear, when I will test my apps on a real server, but now this approach seems to be exactly what I was looking for: I imagine, that on a real server Nginx will pass requests to all the hosts associated with my rack apps to a socket listened by Thin server. So, RackStack will meet only those requests which are addressed to the apps I have in my stack. Any suggestions, improvements of this scheme or alternatives are still appreciated!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to run multiple tiny Ruby (Rack) apps on one server?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USStanislav Pankevich
UserOwnerUserId
1. USStanislav Pankevich
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to run multiple tiny Ruby (Rack) apps on one server?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.