You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/local-emulator.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,7 +100,7 @@ As with the Azure Cosmos DB, the Azure Cosmos Emulator supports only secure comm
100
100
101
101
You can run the emulator on a local network. To enable network access, specify the `/AllowNetworkAccess` option at the [command-line](#command-line-syntax), which also requires that you specify `/Key=key_string` or `/KeyFile=file_name`. You can use `/GenKeyFile=file_name` to generate a file with a random key upfront. Then you can pass that to `/KeyFile=file_name` or `/Key=contents_of_file`.
102
102
103
-
To enable network access for the first time the user should shut down the emulator and delete the emulator’s data directory (%LOCALAPPDATA%\CosmosDBEmulator).
103
+
To enable network access for the first time the user should shut down the emulator and delete the emulator's data directory (%LOCALAPPDATA%\CosmosDBEmulator).
Once you have the Azure Cosmos Emulator running on your desktop, you can use the [Azure Cosmos DB Table API SDK](table-storage-how-to-use-dotnet.md) to interact with the emulator. Start emulator from command prompt as an administrator with “/EnableTableEndpoint”. Next run the following code to connect to the table API account:
128
+
Once you have the Azure Cosmos Emulator running on your desktop, you can use the [Azure Cosmos DB Table API SDK](table-storage-how-to-use-dotnet.md) to interact with the emulator. Start emulator from command prompt as an administrator with "/EnableTableEndpoint". Next run the following code to connect to the table API account:
Start emulator from an administrator command prompt with “/EnableCassandraEndpoint”. Alternatively you can also set the environment variable `AZURE_COSMOS_EMULATOR_CASSANDRA_ENDPOINT=true`.
147
+
Start emulator from an administrator command prompt with "/EnableCassandraEndpoint". Alternatively you can also set the environment variable `AZURE_COSMOS_EMULATOR_CASSANDRA_ENDPOINT=true`.
@@ -174,11 +174,11 @@ Start emulator from an administrator command prompt with “/EnableCassandraEndp
174
174
175
175
### Gremlin API
176
176
177
-
Start emulator from an administrator command prompt with “/EnableGremlinEndpoint”. Alternatively you can also set the environment variable `AZURE_COSMOS_EMULATOR_GREMLIN_ENDPOINT=true`
177
+
Start emulator from an administrator command prompt with "/EnableGremlinEndpoint". Alternatively you can also set the environment variable `AZURE_COSMOS_EMULATOR_GREMLIN_ENDPOINT=true`
* In the emulator’s Data Explorer create a database "db1" and a collection "coll1"; for the partition key, choose "/name"
181
+
* In the emulator's Data Explorer create a database "db1" and a collection "coll1"; for the partition key, choose "/name"
182
182
183
183
* Run the following commands in a regular command prompt window:
184
184
@@ -408,7 +408,7 @@ cd $env:LOCALAPPDATA\CosmosDBEmulator\bind-mount
408
408
.\importcert.ps1
409
409
```
410
410
411
-
Closing the interactive shell once the emulator has been started will shut down the emulator’s container.
411
+
Closing the interactive shell once the emulator has been started will shut down the emulator's container.
412
412
413
413
To open the Data Explorer, navigate to the following URL in your browser. The emulator endpoint is provided in the response message shown above.
414
414
@@ -440,7 +440,7 @@ Finally, we need to import the Emulator CA certificate into the Linux or Mac env
440
440
441
441
If you are working on Linux, .NET relays on OpenSSL to do the validation:
442
442
443
-
1. [Export the certificate in PFX format](./local-emulator-export-ssl-certificates.md#how-to-export-the-azure-cosmos-db-ssl-certificate) (PFX is available when choosing to export the private key).
443
+
1. [Export the certificate in PFX format](./local-emulator-export-ssl-certificates.md#how-to-export-the-azure-cosmos-db-tlsssl-certificate) (PFX is available when choosing to export the private key).
444
444
445
445
1. Copy that PFX file into your Linux environment.
446
446
@@ -466,7 +466,7 @@ If you are working on Linux, .NET relays on OpenSSL to do the validation:
466
466
467
467
Use the following steps if you are working on Mac:
468
468
469
-
1. [Export the certificate in PFX format](./local-emulator-export-ssl-certificates.md#how-to-export-the-azure-cosmos-db-ssl-certificate) (PFX is available when choosing to export the private key).
469
+
1. [Export the certificate in PFX format](./local-emulator-export-ssl-certificates.md#how-to-export-the-azure-cosmos-db-tlsssl-certificate) (PFX is available when choosing to export the private key).
0 commit comments