Skip to content

Commit 00a744d

Browse files
jmd-mongoandf-mongodb
authored andcommitted
DOCS-17576 replaces links to mongosh with binary links
1 parent df8c0d6 commit 00a744d

File tree

357 files changed

+782
-782
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

357 files changed

+782
-782
lines changed

source/administration/configuration.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -236,7 +236,7 @@ among all members of the set. Consider the following:
236236
replSetName: set0
237237

238238
Use descriptive names for sets. Once configured, use
239-
:mongosh:`mongosh </>` to add hosts to the replica set.
239+
:binary:`~bin.mongosh` to add hosts to the replica set.
240240

241241
.. seealso::
242242

source/administration/monitoring.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -499,15 +499,15 @@ has a background :term:`balancer` process that distributes data to ensure that
499499
chunks are always optimally distributed among the :term:`shards <shard>`.
500500

501501
Issue the :method:`db.printShardingStatus()` or :method:`sh.status()`
502-
command to the :binary:`~bin.mongos` from within :mongosh:`mongosh </>`.
502+
command to the :binary:`~bin.mongos` from within :binary:`~bin.mongosh`.
503503
This returns an overview of the entire cluster including the
504504
database name, and a list of the chunks.
505505

506506
Stale Locks
507507
~~~~~~~~~~~
508508

509509
To check the lock status of the database, connect to a
510-
:binary:`~bin.mongos` instance using :mongosh:`mongosh </>`. Issue the
510+
:binary:`~bin.mongos` instance using :binary:`~bin.mongosh`. Issue the
511511
following command sequence to switch to the ``config`` database and
512512
display all outstanding locks on the shard database:
513513

source/appendix/security/appendixA-openssl-ca.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ B. Generate the Test CA PEM File
159159
cat mongodb-test-ca.crt mongodb-test-ia.crt > test-ca.pem
160160

161161
You can use the :red:`test` PEM file when configuring :binary:`~bin.mongod`,
162-
:binary:`~bin.mongos`, or :mongosh:`mongosh </>` for TLS/SSL :red:`testing`.
162+
:binary:`~bin.mongos`, or :binary:`~bin.mongosh` for TLS/SSL :red:`testing`.
163163

164164
You can use the :red:`test` intermediate authority to sign the :red:`test`
165165
certificates for both the server(s) and client(s). A single authority

source/appendix/security/appendixC-openssl-client.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ B. Generate the Test PEM File for Client
133133
cat mongodb-test-client.crt mongodb-test-client.key > test-client.pem
134134

135135
You can use the :red:`test` PEM file to configure
136-
:mongosh:`mongosh </>` for TLS/SSL :red:`testing`. For example, to
136+
:binary:`~bin.mongosh` for TLS/SSL :red:`testing`. For example, to
137137
connect to a :binary:`~bin.mongod` or a :binary:`~bin.mongos`:
138138

139139
.. example::

source/changeStreams.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ You can open change streams against:
6969

7070
The examples on this page use the MongoDB drivers to open and
7171
work with a change stream cursor for a single collection. See
72-
also the :mongosh:`mongosh </>` method
72+
also the :binary:`~bin.mongosh` method
7373
:method:`db.collection.watch()`.
7474

7575
* - A database
@@ -80,7 +80,7 @@ You can open change streams against:
8080
collections.
8181

8282
For the MongoDB driver method, refer to your driver
83-
documentation. See also the :mongosh:`mongosh </>` method
83+
documentation. See also the :binary:`~bin.mongosh` method
8484
:method:`db.watch()`.
8585

8686

@@ -92,7 +92,7 @@ You can open change streams against:
9292
databases except for ``admin``, ``local``, and ``config``.
9393

9494
For the MongoDB driver method, refer to your driver
95-
documentation. See also the :mongosh:`mongosh </>` method
95+
documentation. See also the :binary:`~bin.mongosh` method
9696
:method:`Mongo.watch()`.
9797

9898
.. note:: Change Stream Examples

source/core/authentication-mechanisms.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ To specify the authentication mechanism to use, set the
4646
:binary:`~bin.mongos`.
4747

4848
Clients specify the authentication mechanism in the :method:`db.auth()` method.
49-
For :mongosh:`mongosh </>` and the MongoDB tools, you can also specify the
49+
For :binary:`~bin.mongosh` and the MongoDB tools, you can also specify the
5050
authentication mechanism from the command line.
5151

5252
.. toctree::

source/core/capped-collections.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ Create a Capped Collection
145145

146146
You must create capped collections explicitly using the
147147
:method:`db.createCollection()` method, which is a
148-
:mongosh:`mongosh </>` helper for the :dbcommand:`create` command.
148+
:binary:`~bin.mongosh` helper for the :dbcommand:`create` command.
149149
When creating a capped collection you must specify the maximum size of
150150
the collection in bytes, which MongoDB will pre-allocate for the
151151
collection. The size of the capped collection includes a small amount of

source/core/databases-and-collections.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ gathered together in :term:`collections <collection>`. A
2121
Databases
2222
---------
2323
In MongoDB, databases hold one or more collections of documents. To
24-
select a database to use, in :mongosh:`mongosh </>`, issue the
24+
select a database to use, in :binary:`~bin.mongosh`, issue the
2525
``use <db>`` statement, as in the following example:
2626

2727
.. code-block:: javascript
@@ -34,7 +34,7 @@ Create a Database
3434
If a database does not exist, MongoDB creates the database when you
3535
first store data for that database. As such, you can switch to a
3636
non-existent database and perform the following operation in
37-
:mongosh:`mongosh </>`:
37+
:binary:`~bin.mongosh`:
3838

3939
.. code-block:: javascript
4040

source/core/gridfs.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -287,7 +287,7 @@ exists before read and write operations. See the relevant driver
287287
documentation for the specific behavior of your GridFS application.
288288

289289
If this index does not exist, you can issue the following operation to
290-
create it using :mongosh:`mongosh </>`:
290+
create it using :binary:`~bin.mongosh`:
291291

292292
.. code-block:: javascript
293293

@@ -312,7 +312,7 @@ read and write operations. See the relevant driver documentation for the
312312
specific behavior of your GridFS application.
313313

314314
If this index does not exist, you can issue the following operation to
315-
create it using :mongosh:`mongosh </>`:
315+
create it using :binary:`~bin.mongosh`:
316316

317317
.. code-block:: javascript
318318

source/core/hashed-sharding.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Sharding on a Compound Hashed Index
5050
.. include:: /includes/warning-hashed-index-floating-point.rst
5151

5252
.. [#hashvalue]
53-
Starting in version 4.0, :mongosh:`mongosh </>` provides the
53+
Starting in version 4.0, :binary:`~bin.mongosh` provides the
5454
method :method:`convertShardKeyToHashed()`. This method uses the
5555
same hashing function as the hashed index and can be used to see
5656
what the hashed value would be for a key.

0 commit comments

Comments
 (0)