This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/main by this push:
new 479ac1568 fix(ci): website build
479ac1568 is described below
commit 479ac1568f66d835e736d3b5c73b7ab2b9f7e1a3
Author: Pasquale Congiusti <pasquale.congiu...@gmail.com>
AuthorDate: Wed Sep 4 15:35:28 2024 +0200
fix(ci): website build
---
.../ROOT/{pages => images}/concepts/integrations.png | Bin
docs/modules/ROOT/{pages => images}/concepts/pipes.png | Bin
docs/modules/ROOT/nav.adoc | 2 +-
docs/modules/ROOT/pages/configuration/dependencies.adoc | 6 ++----
docs/modules/ROOT/pages/index.adoc | 2 +-
docs/modules/ROOT/pages/installation/advanced/offline.adoc | 2 +-
docs/modules/ROOT/pages/pipes/pipes.adoc | 2 +-
7 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/docs/modules/ROOT/pages/concepts/integrations.png
b/docs/modules/ROOT/images/concepts/integrations.png
similarity index 100%
rename from docs/modules/ROOT/pages/concepts/integrations.png
rename to docs/modules/ROOT/images/concepts/integrations.png
diff --git a/docs/modules/ROOT/pages/concepts/pipes.png
b/docs/modules/ROOT/images/concepts/pipes.png
similarity index 100%
rename from docs/modules/ROOT/pages/concepts/pipes.png
rename to docs/modules/ROOT/images/concepts/pipes.png
diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
index 475ba5190..38eda62fe 100644
--- a/docs/modules/ROOT/nav.adoc
+++ b/docs/modules/ROOT/nav.adoc
@@ -21,7 +21,7 @@
** xref:running/synthetic.adoc[Synthetic Integrations]
** xref:running/promoting.adoc[Promote an Integration]
* xref:pipes/pipes.adoc[Run an Pipe]
-** xref:pipes/pipes-cli.adoc[kamel bind CLI]
+** xref:pipes/bind-cli.adoc[kamel bind CLI]
** xref:pipes/promoting.adoc[Promote a Pipe]
* xref:languages/languages.adoc[Languages]
** xref:languages/java.adoc[Java]
diff --git a/docs/modules/ROOT/pages/configuration/dependencies.adoc
b/docs/modules/ROOT/pages/configuration/dependencies.adoc
index 039357788..56a002e27 100644
--- a/docs/modules/ROOT/pages/configuration/dependencies.adoc
+++ b/docs/modules/ROOT/pages/configuration/dependencies.adoc
@@ -9,11 +9,9 @@ from("imap://ad...@myserver.com")
.to("seda:output")
```
-Since the integration has a endpoint starting with the **"imap:" prefix**,
Camel K is able to **automatically add the "camel-mail" component** to the list
of required dependencies.
-The `seda:` endpoint belongs to `camel-core` that is automatically added to
all integrations, so Camel K will not add additional dependencies for it.
-This dependency resolution mechanism is transparent to the user, that will
just see the integration running.
+Since the integration has a endpoint starting with the **"imap:" prefix**,
Camel K is able to **automatically add the "camel-mail" component** to the list
of required dependencies. The `seda:` endpoint belongs to `camel-core` that is
automatically added to all integrations, so Camel K will not add additional
dependencies for it. This dependency resolution mechanism is transparent to the
user, that will just see the integration running.
-Automatic resolution is also a nice feature in xref:running/dev-mode.adoc[dev
mode], because you are allowed to add all components you need *without exiting
the dev loop*.
+Automatic resolution is also a nice feature in _dev mode_, because you are
allowed to add all components you need *without exiting the dev loop*.
NOTE: Camel K won't be able to resolve automatically the dependencies when
your routes specify dynamic URIs.
diff --git a/docs/modules/ROOT/pages/index.adoc
b/docs/modules/ROOT/pages/index.adoc
index e9a59c394..48dde87fd 100644
--- a/docs/modules/ROOT/pages/index.adoc
+++ b/docs/modules/ROOT/pages/index.adoc
@@ -43,7 +43,7 @@ ifndef::prerelease[This release will not be updated, but
rather replaced by a ne
endif::[]
--
-From Camel K version 2 onward you will be able to use any Camel K Runtime.
Each runtime depends on a Camel Quarkus, Camel and Quarkus Platform version.
Every Camel K has a default runtime used, but you can
xref:running/runtime-version.adoc[pick any Camel K Runtime available] (backward
and forward compatible).
+From Camel K version 2 onward you will be able to use any Camel K Runtime.
Each runtime depends on a Camel Quarkus, Camel and Quarkus Platform version.
Every Camel K has a default runtime used, but you can
xref:configuration/runtime-version.adoc[pick any Camel K Runtime available]
(backward and forward compatible).
[caption=]
.Camel dependencies matrix
diff --git a/docs/modules/ROOT/pages/installation/advanced/offline.adoc
b/docs/modules/ROOT/pages/installation/advanced/offline.adoc
index d8f7a9fa0..e6d32f6d4 100644
--- a/docs/modules/ROOT/pages/installation/advanced/offline.adoc
+++ b/docs/modules/ROOT/pages/installation/advanced/offline.adoc
@@ -11,7 +11,7 @@ We can easily identify those components which requires access
to the Internet an
[[registry]]
== Container images registry
-The xref:installation/registry/registry.adoc[registry] is the component in
charge to host the containers which are built from the operator and are used by
the cluster to run the Camel applications. This component could be provided out
of the box by the cluster, or should be operated by you (see the guide on
xref:installation/registry/own.adoc[how to run your own registry]).
+The xref:installation/registry/registry.adoc[registry] is the component in
charge to host the containers which are built from the operator and are used by
the cluster to run the Camel applications. This component could be provided out
of the box by the cluster, or should be operated by you (see the guide on
xref:installation/registry/special/own.adoc[how to run your own registry]).
As we're in a disconnected environment, we assume this component to be
accessible by the cluster (through an IP or URL). However, the cluster need to
use the Camel K container image in order to be installed. You therefore need to
make sure that the cluster registry has preloaded the Camel K container image,
which is `docker.io/apache/camel-k:2.3.0` (or any version you're willing to
use).
diff --git a/docs/modules/ROOT/pages/pipes/pipes.adoc
b/docs/modules/ROOT/pages/pipes/pipes.adoc
index b38bdc677..c54f51094 100644
--- a/docs/modules/ROOT/pages/pipes/pipes.adoc
+++ b/docs/modules/ROOT/pages/pipes/pipes.adoc
@@ -125,4 +125,4 @@ spec:
== Using Kamel CLI
-Camel K works very well with any Kubernetes compatible user interface (such as
CLI as `kubectl`, `oc` or any other visual tooling). However we do provide a
simple CLI that helps you performing most of the Pipe works in an easier
fashion: it's xref:running/bind-cli.adoc[`kamel` CLI].
+Camel K works very well with any Kubernetes compatible user interface (such as
CLI as `kubectl`, `oc` or any other visual tooling). However we do provide a
simple CLI that helps you performing most of the Pipe works in an easier
fashion: it's xref:pipes/bind-cli.adoc[`kamel` CLI].
