Re:Answers to common questions about RethinkDB
by coffeemug on Friday November 16, 2012 @04:05PM
(#4795838)
slava@rethink here - thanks for setting this up! Is this running on ec2 or on your local infrastructure?
Re:Answers to common questions about RethinkDB
by themgt on Friday November 16, 2012 @04:24PM
(#4795935)
thanks for making it! it's our platform built around heroku's open-sourced toolchain, so we made a little buildpack + app repo w/ Procfile, compiled into a slug and then deployed it out like everything else
Re:Answers to common questions about RethinkDB
by coffeemug on Friday November 16, 2012 @05:47PM
(#4796275)
Could you shoot me an e-mail to [email protected]? We're looking into building a Heroku plugin, and I'd love to chat about potential solutions to this (we're new to Heroku here).
Re:Answers to common questions about RethinkDB
by woogley on Friday November 16, 2012 @04:03PM
(#4795835)
Thanks, but word of warning - through the Data Explorer interface it is possible to take down a core or two by passing things like 'while (1) {}' to the r.js() command
No good deed goes unpunished, etc.
Re:Answers to common questions about RethinkDB
by coffeemug on Friday November 16, 2012 @04:06PM
(#4795844)
Hey, it's actually not very difficult for us to make this more robust (e.g. kill and restart the v8 process if it gets out of line). EDIT: here's an issue for this -- https://github.com/rethinkdb/rethinkdb/issues/69
We'll fix this ASAP (though this is somewhat of a low priority).
Re:Answers to common questions about RethinkDB
by jdoliner on Friday November 16, 2012 @04:09PM
(#4795857)
There are actually really cool insidious queries you can run. There is for example a query you can run which will insert an infinite number of documents into a table!! Hats off to the first person to post it.
It's awesome that you're hosting this you should just be sure it's on a machine you're not depending on for other services.
We ran into a little bug w/ the ajax requests using the wrong port when run behind an nginx reverse proxy, and the team was very helpful and responsive in getting it fixed: https://github.com/rethinkdb/rethinkdb/issues/63
Seems like a very promising project