This tutorial should really encourage the user to type various commands as part of the tutorial, rather than allowing progress by just typing "next" over and over again. The great thing about the try-ruby tutorial was that it actually gets you to type ruby commands to get to the next bit, thus forcing you to try out the syntax rather than just read a tutorial.

I like this idea. Interactivity was on my mind while I was implementing the current version. There's lots of ways to improve the actual teaching process it offers, and it's something I'm interested in continuing to develop.

I guess you only saw trymongo but never experienced the original TryRuby? If not, please take a look at it :)

Another thing would be nice is if it was possible to click the sample commands and have them added to the command line history and executed, to save a bit on typing.

It's also nice to not be forced to type in every single command and just to skip ahead if something looks obvious or you're getting bored.

I liked this - a quick summary of what Redis can offer, better than skimming a lot of "NoSQL is better" articles. Would be interesting if the tutorial mentioned some of the scenarios why Redis is better than standard SQL at the end though. I'm left thinking - interesting, but what's the advantage over what I know already. All the sets, ordered sets, and so on can be done fairly straightforwardly in SQL. Examples of performance guarantees / benefits for example.

This _DOES_ let you type commands.

set fu 1

incr fu

It lets you type them, it doesn't ask you to type them.

The Try-ruby tutorial asks you to type ruby statements to get to the next step.

  The blue window above is a Ruby prompt. Type a line of Ruby code, hit Enter and watch it run!

  For example, try typing some math. Like: 2 + 6

See http://tryruby.org/ before talking further, please.

I have never used Redis, or any other NoSQL database before, but have always been interested. I actually went through the whole tutorial, and now I feel like I have a better understanding of what all the fuss is about.

That being said, and this is outside the scope of the tutorial, but how are these key/data/NoSQL stores at storing up a large value (think of a TEXT or BLOB column)? Just curious...

For redis specifically, the maximum size of a value for a key is 1GB - http://code.google.com/p/redis/wiki/SetCommand

Being able to press the up key in the input textbox to scroll through your previous "commands" is a nice touch.

Yeah, I pressed the up key out of habit and was pleasantly surprised to find it did what I expected

That was quick :-)

http://twitter.com/antirez/status/9597858680

Slicehost donated the vps it's hosted on.

We can use the command SET to store the value "bar" at key foo:

    SET server:name "fido"

Please, please, pretty please, make your examples match the text that tells you what the example does.

I fixed this item. Thanks for the feedback! :-)

Needs tab completion or a button to go next. Compared to reading docs this was already boring/waste of time after typing TUTORIAL and NEX...

The up arrow works.