Skip to content

Commit f756a0e

Browse files
authored
Merge pull request #276055 from MSFTeegarden/patch-66
Correct cache development FAQ page
2 parents 3b0966f + e34592a commit f756a0e

File tree

3 files changed

+10
-22
lines changed

3 files changed

+10
-22
lines changed

articles/azure-cache-for-redis/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@
172172
href: cache-administration.md#reboot
173173
- name: Update channel and schedule updates
174174
href: cache-administration.md#update-channel-and-schedule-updates
175-
- name: Configure redis-cli.exe access
175+
- name: Configure redis-cli access
176176
href: cache-how-to-redis-cli-tool.md
177177
- name: Create and manage a cache using CLI
178178
href: cache-manage-cli.md
@@ -333,4 +333,4 @@
333333
- name: Scaling
334334
href: cache-best-practices-scale.md
335335
- name: Server load management
336-
href: cache-best-practices-server-load.md
336+
href: cache-best-practices-server-load.md

articles/azure-cache-for-redis/cache-development-faq.yml

Lines changed: 3 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ sections:
7171
- question: |
7272
Is there a local emulator for Azure Cache for Redis?
7373
answer: |
74-
There's no local emulator for Azure Cache for Redis. You can run the MSOpenTech version of redis-server.exe from the [Redis command-line tools](https://github.com/MSOpenTech/redis/releases/) on your local machine. Then, connect to it to get a similar experience to a local cache emulator, as shown in the following example:
74+
There's no local emulator for Azure Cache for Redis. You can, however, run a copy of community Redis on your local machine and connect to it to get a similar experience to a local cache emulator, as shown in the following example:
7575
7676
```csharp
7777
private static Lazy<ConnectionMultiplexer>
@@ -91,7 +91,7 @@ sections:
9191
}
9292
```
9393
94-
You can optionally configure a [redis.conf](https://redis.io/topics/config) file to more closely match the [default cache settings](cache-configure.md#default-redis-server-configuration) for your online Azure Cache for Redis if you want.
94+
Redis runs natively on Linux, but you can also use Windows Subsystem for Linux to run Redis on a windows machine. For more information, see [Install Redis on Windows](https://redis.io/docs/latest/operate/oss_and_stack/install/install-redis/install-redis-on-windows/) You can optionally configure a [redis.conf](https://redis.io/topics/config) file to more closely match the [default cache settings](cache-configure.md#default-redis-server-configuration) for your online Azure Cache for Redis if you want.
9595
9696
- question: |
9797
How can I run Redis commands?
@@ -100,19 +100,7 @@ sections:
100100
101101
If you have a Standard or Premium cache, you can run Redis commands using the [Redis Console](cache-configure.md#redis-console). The Redis console provides a secure way to run Redis commands in the Azure portal.
102102
103-
You can also use the Redis command-line tools. To use them, do the following steps:
104-
1. Download the [Redis command-line tools](/azure/azure-cache-for-redis/cache-how-to-redis-cli-tool#install-redis-cli).
105-
106-
1. Connect to the cache using `redis-cli.exe`.
107-
108-
1. Pass in the cache endpoint using the -h switch and the key using -a as shown in the following example:
109-
110-
`redis-cli -h <Azure Cache for Redis name>.redis.cache.windows.net -a <key>`
111-
112-
> [!NOTE]
113-
> The Redis command-line tools don't work with the TLS port, but you can use a utility such as `stunnel` to securely connect the tools to the TLS port by following the directions in the [How to use the Redis command-line tool with Azure Cache for Redis](./cache-how-to-redis-cli-tool.md) article.
114-
>
115-
>
103+
You can also use the Redis command-line tools. To use them, see [Use the Redis command-line tool with Azure Cache for Redis](cache-how-to-redis-cli-tool.md)
116104
117105
- question: |
118106
Why doesn't Azure Cache for Redis have an MSDN class library reference?

articles/azure-cache-for-redis/cache-how-to-redis-cli-tool.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -55,31 +55,31 @@ Open up a shell or terminal on a computer with the _Redis package_ installed. If
5555
1. Use the following command to connect to a Basic, Standard, or Premium tier Azure Cache for Redis instance using TLS:
5656

5757
```console
58-
redis-cli.exe -p 6380 -h yourcachename.redis.cache.windows.net -a YourAccessKey --tls
58+
redis-cli -p 6380 -h yourcachename.redis.cache.windows.net -a YourAccessKey --tls
5959
```
6060

6161
1. Connect to a Basic, Standard, or Premium tier Azure Cache for Redis instance that doesn't use TLS:
6262

6363
```console
64-
redis-cli.exe -p 6379 -h yourcachename.redis.cache.windows.net -a YourAccessKey
64+
redis-cli -p 6379 -h yourcachename.redis.cache.windows.net -a YourAccessKey
6565
```
6666

6767
1. Connect to a Basic, Standard, or Premium tier Azure Cache for Redis instance using TLS and clustering:
6868

6969
```console
70-
redis-cli.exe -p 6380 -h yourcachename.redis.cache.windows.net -a YourAccessKey --tls -c
70+
redis-cli -p 6380 -h yourcachename.redis.cache.windows.net -a YourAccessKey --tls -c
7171
```
7272

7373
1. Connect to an Enterprise or Enterprise Flash tier cache instance using Enterprise cluster policy with TLS:
7474

7575
```console
76-
redis-cli.exe -p 10000 -h yourcachename.eastus.redisenterprise.cache.azure.net -a YourAccessKey --tls
76+
redis-cli -p 10000 -h yourcachename.eastus.redisenterprise.cache.azure.net -a YourAccessKey --tls
7777
```
7878

7979
1. Connect to an Enterprise or Enterprise Flash tier cache instance using OSS cluster policy without TLS:
8080

8181
```console
82-
redis-cli.exe -p 10000 -h yourcachename.eastus.redisenterprise.cache.azure.net -a YourAccessKey -c
82+
redis-cli -p 10000 -h yourcachename.eastus.redisenterprise.cache.azure.net -a YourAccessKey -c
8383
```
8484

8585
### Testing the connection

0 commit comments

Comments
 (0)