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: _docs/installation/runtime-architecture.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -196,9 +196,9 @@ Each microservice within the Codefresh Pipeline and GitOps modules has its own d
196
196
197
197
198
198
##Codefresh Runner architecture
199
-
This section shows a detailed view of the Codefresh Runner architecture, and a description of the components. See[Runner installation behind firewalls]({{site.baseurl}}/docs/installation/behind-the-firewall/).
199
+
<!--- This section shows a detailed view of the Codefresh Runner architecture, and a description of the components. See also [Runner installation behind firewalls]({{site.baseurl}}/docs/installation/behind-the-firewall/).-->
200
+
200
201
201
-
DIAGRAM TO BE INSERTED
202
202
203
203
204
204
The Codefresh Runner includes two main components:
@@ -238,7 +238,7 @@ Optional. When installed, provides visibility on cluster resources in Codefresh,
238
238
Another optional component, the App-Proxy serves as an extension to the Codefresh platform. Its purpose is to enable remote operations, such as displaying Git repositories for Git providers behind firewalls and creating webhooks, while maintaining security.
239
239
240
240
241
-
###Codefresh Platform
241
+
###Clients
242
242
243
243
Codefresh offers a[public API]({{site.baseurl}}/docs/integrations/codefresh-api/), consumed both by the Web user interface and the[Codefresh CLI](https://codefresh-io.github.io/cli/){:target="\_blank"}. The API is also available for any custom integration with external tools or services.