Skip to content

Commit 3ed3cff

Browse files
authored
Add missing aliases (#2114)
1 parent 0450701 commit 3ed3cff

File tree

12 files changed

+16
-2
lines changed

12 files changed

+16
-2
lines changed

modules/ROOT/pages/authentication-authorization/index.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
= Authentication and authorization
44
:description: An overview of authentication and authorization in Neo4j.
55
:keywords: authentication, authorization, security, access control, roles, privileges, users, LDAP, Active Directory, Kerberos, SSO, single sign-on, authentication plugins, authentication providers, native auth provider, LDAP auth provider, Kerberos auth provider, SSO auth provider, custom auth provider, custom auth plugin, custom auth plugins, custom auth providers, custom authentication plugin, custom authentication plugins, custom authentication providers, custom authorization plugin, custom authorization plugins, custom authorization providers, custom authorisation plugin, custom authorisation plugin
6+
:page-aliases: authentication-authorization/introduction.adoc, authentication-authorization/terminology.adoc
67

78
This page provides an overview of authentication and authorization in Neo4j.
89

modules/ROOT/pages/cloud-deployments/neo4j-gcp.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
11
:description: Deploy Neo4j on Google Cloud Platform (GCP) directly from the GCP Marketplace or by using the Neo4j Deployment Manager templates hosted on GitHub.
2+
:page-aliases: cloud-deployments/neo4j-gcp/index.adoc, cloud-deployments/neo4j-gcp/single-instance-vm.adoc, cloud-deployments/neo4j-gcp/causal-cluster-vm.adoc, cloud-deployments/neo4j-gcp/automation-gcp.adoc
3+
24
[[gcp]]
35
= Neo4j on GCP
46

modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
11
:description: This section covers the use of `SHOW DATABASES`, and other related Cypher commands.
2+
:page-aliases: monitoring/individual-db-states.adoc
3+
24
[role=enterprise-edition]
35
[[show-databases-monitoring]]
46
= Monitor databases

modules/ROOT/pages/clustering/setup/deploy.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
:description: This section describes how to deploy a Neo4j cluster.
2-
:page-aliases: clustering/deploy.adoc
2+
:page-aliases: clustering/deploy.adoc, tutorial/local-causal-cluster.adoc
33
[role=enterprise-edition]
44
[[clustering-deploy]]
55
= Deploy a basic cluster

modules/ROOT/pages/database-administration/routing-decisions.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
[[routing-decisions]]
33
= Query routing decisions
44
:description: This page describes in detail how queries are routed to databases for execution.
5+
:page-aliases: routing-decisions.adoc
56

67
Query routing is the process of deciding which Cypher executor (database) should be used and at which physical location the query should be executed.
78
Every query that arrives at a Neo4j server, over the bolt protocol from a driver, undergoes the process described here.

modules/ROOT/pages/database-internals/transaction-management.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
:description: How transactions work in Neo4j and how to configure transactional behavior.
2+
:page-aliases: monitoring/transaction-management.adoc
13
[[transaction-management]]
24
= Transaction management
35

modules/ROOT/pages/docker/backup-restore.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
11
:description: Backup and restore operations when running Neo4j in a Docker container.
2+
:page-aliases: docker/maintenance.adoc
3+
24
[role=enterprise-edition]
35
[[docker-neo4j-backup-restore]]
46
= Back up and restore a Neo4j database (online)

modules/ROOT/pages/docker/dump-load.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
:description: Dump and load operations when running Neo4j in a Docker container.
2+
23
[[docker-neo4j-dump]]
34
= Dump and load a Neo4j database (offline)
45

modules/ROOT/pages/kubernetes/accessing-neo4j.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
[[accessing-neo4j]]
22
= Accessing Neo4j
33
:description: How to access Neo4j running in Kubernetes.
4+
:page-aliases: kubernetes/accessing-cluster.adoc
45

56
A Neo4j running on Kubernetes is accessible via Kubernetes Services.
67
Neo4j has a number of different interfaces for different application and operational purposes.

modules/ROOT/pages/procedures.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
:table-caption!:
55
:table-stripes: hover
66
:table-frame: topbot
7-
7+
:page-aliases: /reference/procedures.adoc
88
:stem:
99
:mathjax-tex-packages: ams
1010

0 commit comments

Comments
 (0)