This is an automated email from the ASF dual-hosted git repository.
bbender pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode-native.git
The following commit(s) were added to refs/heads/develop by this push:
new c685fd9 GEODE-4728: User guide - modify syntax for links to server
and api docs (#462)
c685fd9 is described below
commit c685fd965d5656287719767d2cce5797ac034932
Author: Blake Bender <[email protected]>
AuthorDate: Tue Mar 12 10:02:31 2019 -0700
GEODE-4728: User guide - modify syntax for links to server and api docs
(#462)
---
docs/geode-native-docs/about-client-users-guide.html.md.erb | 2 +-
docs/geode-native-docs/configuring/config-client-cache.html.md.erb | 4 ++--
docs/geode-native-docs/configuring/configuration.html.md.erb | 2 +-
docs/geode-native-docs/configuring/sysprops.html.md.erb | 4 ++--
docs/geode-native-docs/continuous-queries.html.md.erb | 2 +-
docs/geode-native-docs/function-execution.html.md.erb | 2 +-
.../getting-started/getting-started-nc-client.html.md.erb | 6 +++---
docs/geode-native-docs/regions/region-attributes.html.md.erb | 5 ++---
docs/geode-native-docs/serialization/data-serialization.html.md.erb | 2 +-
9 files changed, 14 insertions(+), 15 deletions(-)
diff --git a/docs/geode-native-docs/about-client-users-guide.html.md.erb
b/docs/geode-native-docs/about-client-users-guide.html.md.erb
index f071dda..e55f621 100644
--- a/docs/geode-native-docs/about-client-users-guide.html.md.erb
+++ b/docs/geode-native-docs/about-client-users-guide.html.md.erb
@@ -28,5 +28,5 @@ See the API docs for API details:
- [C++ API docs](https://geode.apache.org/releases/latest/cppdocs/index.html)
- [.NET API
docs](https://geode.apache.org/releases/latest/dotnetdocs/index.html)
-See the [_<%=vars.product_name_long%> User
Guide_](/serverman/about_<%=vars.product_name.downcase%>.html) for information
regarding the server.
+See the [_<%=vars.product_name_long%> User
Guide_](serverman/about_<%=vars.product_name.downcase%>.html) for information
regarding the server.
diff --git a/docs/geode-native-docs/configuring/config-client-cache.html.md.erb
b/docs/geode-native-docs/configuring/config-client-cache.html.md.erb
index 79829fc..c63539d 100644
--- a/docs/geode-native-docs/configuring/config-client-cache.html.md.erb
+++ b/docs/geode-native-docs/configuring/config-client-cache.html.md.erb
@@ -32,6 +32,6 @@ Regions are created from `Cache` instances. Regions provide
the entry points to
instances of `Region` and `RegionEntry`.
For more information specific to your client programming language, see the
-[C++ Client API](https://gemfire-nc-100-cppdocs.cfapps.io) or the
-[.NET Client API](https://gemfire-nc-100-dotnetdocs.cfapps.io).
+[C++ Client API](cppdocs) or the
+[.NET Client API](dotnetdocs).
diff --git a/docs/geode-native-docs/configuring/configuration.html.md.erb
b/docs/geode-native-docs/configuring/configuration.html.md.erb
index ad797a1..e421970 100644
--- a/docs/geode-native-docs/configuring/configuration.html.md.erb
+++ b/docs/geode-native-docs/configuring/configuration.html.md.erb
@@ -65,6 +65,6 @@ When redundancy is enabled, secondary servers maintain queue
backups while the p
events to the client. If the primary server fails, one of the secondary
servers steps in as primary
to provide uninterrupted event messaging to the client.
To configure high availability, set the `subscription-redundancy` in the
client’s pool configuration. This setting indicates the number of secondary
servers to use.
-See the _<%=vars.product_name%> User Guide_ section [Configuring Highly
Available
Servers](/serverman/developing/events/configuring_highly_available_servers.html)
+See the _<%=vars.product_name%> User Guide_ section [Configuring Highly
Available
Servers](serverman/developing/events/configuring_highly_available_servers.html)
for more details.
diff --git a/docs/geode-native-docs/configuring/sysprops.html.md.erb
b/docs/geode-native-docs/configuring/sysprops.html.md.erb
index 890c7e6..891dea6 100644
--- a/docs/geode-native-docs/configuring/sysprops.html.md.erb
+++ b/docs/geode-native-docs/configuring/sysprops.html.md.erb
@@ -21,8 +21,8 @@ limitations under the License.
A variety of system properties can be specified when a client connects to a
distributed system, either programmatically or in a `geode.properties` file.
-- In the [.NET API docs](https://gemfire-nc-100-dotnetdocs.cfapps.io), see
`Apache::Geode::Client::SystemProperties`.
-- In the [C++ API docs](https://gemfire-nc-100-cppdocs.cfapps.io), see
`apache::geode::client::SystemProperties`.
+- In the [.NET API docs](dotnetdocs), see
`Apache::Geode::Client::SystemProperties`.
+- In the [C++ API docs](cppdocs), see
`apache::geode::client::SystemProperties`.
The following settings can be configured:
diff --git a/docs/geode-native-docs/continuous-queries.html.md.erb
b/docs/geode-native-docs/continuous-queries.html.md.erb
index dd9fdc2..dc787f5 100644
--- a/docs/geode-native-docs/continuous-queries.html.md.erb
+++ b/docs/geode-native-docs/continuous-queries.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
The C++ and .NET clients can initiate queries that run on the
<%=vars.product_name%> cache server
and notify the client when the query results have changed. For details on the
server-side setup for
-continuous queries, see [How Continuous Querying
Works](/serverman/developing/continuous_querying/how_continuous_querying_works.html)
+continuous queries, see [How Continuous Querying
Works](serverman/developing/continuous_querying/how_continuous_querying_works.html)
in the *<%=vars.product_name%> User Guide*.
## <a id="cq_main_features" ></a>Continuous Query Basics
diff --git a/docs/geode-native-docs/function-execution.html.md.erb
b/docs/geode-native-docs/function-execution.html.md.erb
index 3e09528..010d07a 100644
--- a/docs/geode-native-docs/function-execution.html.md.erb
+++ b/docs/geode-native-docs/function-execution.html.md.erb
@@ -28,7 +28,7 @@ To be callable from your client, a function must be
- resident on the server, and
- registered as available for client access.
-See [Executing a Function in
<%=vars.product_name_long%>](/serverman/developing/function_exec/function_execution.html)
+See [Executing a Function in
<%=vars.product_name_long%>](serverman/developing/function_exec/function_execution.html)
in the <%=vars.product_name%> User Guide for details on how to write and
register server-resident functions.
## <a id="client_side_requirements"></a>Client-side Requirements
diff --git
a/docs/geode-native-docs/getting-started/getting-started-nc-client.html.md.erb
b/docs/geode-native-docs/getting-started/getting-started-nc-client.html.md.erb
index 5b45ff8..aeed8f9 100644
---
a/docs/geode-native-docs/getting-started/getting-started-nc-client.html.md.erb
+++
b/docs/geode-native-docs/getting-started/getting-started-nc-client.html.md.erb
@@ -27,8 +27,8 @@ You can choose whether to use a large, remote,
production-quality cluster; a sma
development cluster; or something in-between, such as a testing or
experimental lab installation.
In the _<%=vars.product_name%> User's Guide_,
-see [Configuring and Running a
Cluster](/serverman/configuring/chapter_overview.html)
-and [Client/Server
Configuration](/serverman/topologies_and_comm/cs_configuration/chapter_overview.html)
for instructions on setting up and starting the cluster for a client/server
configuration.
+see [Configuring and Running a
Cluster](serverman/configuring/chapter_overview.html)
+and [Client/Server
Configuration](serverman/topologies_and_comm/cs_configuration/chapter_overview.html)
for instructions on setting up and starting the cluster for a client/server
configuration.
### <a id="connecting_to_server"></a>Connecting to the Server
@@ -99,7 +99,7 @@ Create a named pool of network connections, and instantiate a
region of the desi
var region = regionFactory.Create<string, string>("example_userinfo"); //
create a connection to the region "example_userinfo" on the server
```
-See the _<%=vars.product_name%> User Guide_ section [Configuring a
Client/Server
System](/serverman/topologies_and_comm/cs_configuration/setting_up_a_client_server_system.html)
+See the _<%=vars.product_name%> User Guide_ section [Configuring a
Client/Server
System](serverman/topologies_and_comm/cs_configuration/setting_up_a_client_server_system.html)
for more details.
diff --git a/docs/geode-native-docs/regions/region-attributes.html.md.erb
b/docs/geode-native-docs/regions/region-attributes.html.md.erb
index 6460316..eeb68f2 100644
--- a/docs/geode-native-docs/regions/region-attributes.html.md.erb
+++ b/docs/geode-native-docs/regions/region-attributes.html.md.erb
@@ -1,7 +1,6 @@
---
title: Region Attributes
---
-
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
@@ -23,14 +22,14 @@ Region attributes govern the automated management of a
region and its entries.
Region attribute settings determine where the data resides, how the region is
managed in memory, and the automatic loading, distribution, and expiration of
region entries.
-## <a id="specifying-region-attributes"></a>Specifying Region Attributes
+## <a id="specifying-region-attributes" class="no-quick-link"></a>Specifying
Region Attributes
Specify region attributes before creating the region. You can do this either
through the API or
through the declarative XML file. The API includes classes for defining a
region's attributes before
creation and for modifying some attributes after creation. For details, see
the API for
`RegionShortcut`, `RegionAttributes`, `RegionAttributesFactory`, and
`AttributesMutator`.
-## <a id="region-shortcuts"></a>Region Shortcuts
+## <a id="region-shortcuts" class="no-quick-link"></a>Region Shortcuts
<%=vars.product_name%> provides predefined, shortcut region attributes
settings for your use in `RegionShortcut`.
The shortcuts are:
diff --git
a/docs/geode-native-docs/serialization/data-serialization.html.md.erb
b/docs/geode-native-docs/serialization/data-serialization.html.md.erb
index 10366b9..6ed5a60 100644
--- a/docs/geode-native-docs/serialization/data-serialization.html.md.erb
+++ b/docs/geode-native-docs/serialization/data-serialization.html.md.erb
@@ -25,5 +25,5 @@ Data in your client application's <%=vars.product_name%>
cache must be serializa
between processes, of which **<%=vars.product_name%> Portable Data eXchange
(PDX) serialization** offers
the best combination of versatility and ease-of-use for most applications.
-To learn more about other serialization options, see the [Data Serialization
section in the _<%=vars.product_name_long%> User
Guide_](/serverman/developing/data_serialization/chapter_overview.html).
+To learn more about other serialization options, see the [Data Serialization
section in the _<%=vars.product_name_long%> User
Guide_](serverman/developing/data_serialization/chapter_overview.html).
