Try Redis commands without saving

Run commands in the Console on the sample cache, or on a practice cache that is yours alone, with nothing saved for the team.

In short

Run Redis commands and read the replies without connecting a server of your own. The "Console" tab works like redis-cli on the sample cache, which holds example keys. When you may not add the sample cache to a shared workspace, Cache Tester opens on a practice cache instead, "Try it (not saved)", held for you alone.

Before you start

• Who: anyone with Cache Tester on. The practice cache is yours alone.
• Plan: practice commands are not counted against your plan; the Console on the sample cache follows the plan's usual limits.
• First: nothing to connect. The first screen offers the sample cache.

Steps

1. Open Cache Tester and choose the "Console" tab. On your first visit, press "Run a command" on the "Sample cache" card, with GET greeting ready in "Command", and the Console opens with the reply.
2. Type a command after the prompt, such as GET greeting. On an empty console, press one of "Commands to start from" instead: INFO memory, DBSIZE, SCAN 0 COUNT 20 or TTL <key>.
3. Press "Run", or Enter. The reply reads the way redis-cli prints it, with the time it took.
4. Press the Up and Down keys to recall earlier lines. Press "Clear" to empty the console.

Result: you have run real commands without connecting a server. "Connect Redis" on the first screen is the way to your own.

When you may not add the sample

If you may not add the sample cache to a shared workspace, the first screen shows "Try it (not saved)", marked "Only you", instead of the "Sample cache" card.

1. The "Command" box is ready with GET greeting. Press "Run", or press one of the "Example commands" to try another kind of key.
2. Read the reply the way redis-cli prints it, and the line "Keys here" for what the practice cache holds.
3. To go back to the starting keys, press "Start over".

Good to know

• The practice cache is held for you and this workspace only; nobody else sees your changes, and no saved connection can point at it.
• The command rules are the console's: reads anywhere, writes to this cache, and dangerous commands never.
• Commands that write are recorded in the audit trail on a connection. Practice commands are not audited or counted against your plan, but the usual limit on commands a minute applies.

If something goes wrong

• "The command did not work": read the reply; the command may be one the console never forwards.
• The keys look different from before: you pressed "Start over", which brings the example keys back.

Related

• /help/cache-tester/start-here
• /help/cache-tester/raw-commands-safety-and-audit
• /help/settings/examples