Timeline for Script for starting a rails app, with some peculiarities
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
| Nov 18, 2013 at 20:07 | history | edited | CMW | CC BY-SA 3.0 |
Credit where credit is due
|
| Nov 18, 2013 at 8:43 | vote | accept | Marcus | ||
| Nov 16, 2013 at 20:27 | comment | added | CMW | Yeah, I mentioned that one in my answer. It was not necessary for me since my browser took a while to start and the server was ready by then. Glad you managed to figure it out. | |
| Nov 16, 2013 at 15:25 | comment | added | Marcus | I've actually found a workaround - the WEBrick.run {|server|} variable can be stored in the thread local storage. immediately afterwards, it can be polled at intervals, until it's not nil. at that point, the server is ready. | |
| Nov 16, 2013 at 15:17 | comment | added | Marcus | The logic is appropriate, but there is a bug! The completion of the application start is asynchronous, so that the browser starts before actually something is listening on the port. In addition to that, the webrick shutdown raises an error if the app is not fully started! | |
| Nov 16, 2013 at 14:37 | vote | accept | Marcus | ||
| Nov 16, 2013 at 15:01 | |||||
| Nov 5, 2013 at 15:02 | history | answered | CMW | CC BY-SA 3.0 |