StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17496025
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-05T19:53:30.853
FavoriteCount
0
LastActivityDate
2013-07-05T19:53:30.853
LastEditDate
LastEditorUserId
0
OwnerUserId
535171
ParentId
6807268
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
There's probably more than one way to do this, but this is working for me right now: <h1>The command</h1> <pre><code>port = `lsof -p #{Process.pid} -ai TCP -as TCP:LISTEN -Fn | grep ^n | cut -c 4- | uniq`.strip </code></pre> Note that you'll have to do this at some point after the app has loaded - i.e., you can't use this in your <code>environment.rb</code> or <code>application.rb</code> file. <h1>The explanation</h1> Basically what this command does is as follows: <ul> <li><code>lsof</code> is the Unix command for LiSt Open Files</li> <li><code>-p #{Process.pid}</code> limits it to the current process (i.e., your test web server instance)</li> <li><code>-ai TCP</code> limits it to "files" of type TCP (i.e., open TCP ports). (Note: the <code>-a</code> is to make it AND the search with the pid one - the default, using just <code>-i</code> would OR the search)</li> <li><code>-as TCP:LISTEN</code> limits to just TCP ports that are being listened on (as opposed to any open port - like your app's connection to Postgres for example)</li> <li><code>-Fn</code> tells it to only output the "name" column, which in this case will be the IP/port that is being listened on</li> </ul> The output of that part by itself will be something like this: <pre><code>p12345 n*:5001 n*:5001 </code></pre> The first line, starting with <code>p</code> is the process ID. There's no way to suppress this. The next 2 lines (not sure why it can output multiples, but we'll take care of it in a minute) are the "name" column (hence <code>n</code>), followed by the IP + port. In our case (and I imagine yours as well, in a test environment), the web server listens on all available local IPs, thus <code>*</code>. Then it tells us that the port is, in this case 5001. Finally, we pipe it through... * <code>grep ^n</code> to eliminate the first line (the process id) * <code>cut</code> to say "cut from columns 4 on" - i.e., remove the <code>n*:</code> to return just the port, and * <code>uniq</code> to just get the one instance (It will also have a trailing newline, thus the <code>strip</code> call.) <h1>The usage</h1> In my case, I'm using this in my Cucumber <code>env.rb</code> thusly, to reconfigure the URL options for ActiveMailer so my email links get generated properly as working links in test: port = <code>lsof -p #{Process.pid} -ai TCP -as TCP:LISTEN -Fn | grep ^n | cut -c 4- | uniq</code>.strip MyApp::Application.configure do config.action_mailer.default_url_options[:host] = "0.0.0.0:#{port}" end No doubt you could do the same thing in a helper/config for Rspec as well. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails port of testing environment
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJKubecki
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.