[mrkurt]

Wow, it gets even more interesting:

  /tmp $ cd redis-2.2.8/
  /tmp/redis-2.2.8 $ make
  /tmp/redis-2.2.8 $ cd src
  /tmp/redis-2.2.8/src $ ./redis-server 
  [295] 31 May 15:36:30 # Warning: no config file specified, using the default config. In   order to specify a config file use 'redis-server /path/to/redis.conf'
  [295] 31 May 15:36:30 * Server started, Redis version 2.2.8
  [295] 31 May 15:36:30 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
  [295] 31 May 15:36:30 * The server is now ready to accept connections on port 6379
  [295] 31 May 15:36:30 - 0 clients connected (0 slaves), 790480 bytes in use
  [295] 31 May 15:36:35 - 0 clients connected (0 slaves), 790480 bytes in use
  [295] 31 May 15:36:40 - 0 clients connected (0 slaves), 790480 bytes in use

[adw]

Absolutely none of this is officially supported, right? (It looks very much like "game on, DotCloud", from what you've been finding, though....)

[mrkurt]

I don't think any of it's supported. Redis will run, but you can't exactly get to it (no TCP routing mesh apparently). It really just seems like they made it really easy to add new languages.

[windle]

This is because running commands is from a one-off dyno vs. the formation dyno's that have requests routed to them.

See: http://devcenter.heroku.com/articles/oneoff-admin-ps