Skip to content

Commit 06c5acc

Browse files
authored
chore: add warning message about starting openvsx workspace (#2959)
* chore: add warning message about starting openvsx workspace Signed-off-by: Valeriy Svydenko <[email protected]> * fix typo Signed-off-by: Valeriy Svydenko <[email protected]> --------- Signed-off-by: Valeriy Svydenko <[email protected]>
1 parent a87cfe1 commit 06c5acc

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

modules/administration-guide/pages/running-the-open-vsx-on-premises.adoc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,11 @@ Follow the instructions below to deploy and configure an on-premises Eclipse Ope
2121
+
2222
Create a workspace by using the following link:https://github.com/eclipse/openvsx[Eclipse Open VSX repository].
2323
+
24+
[WARNING]
25+
====
26+
The link:https://github.com/eclipse/openvsx/blob/master/.devfile.yaml[.devfile.yaml] includes an `elasticsearch` component that does not support IBM Power (ppc64le) or IBM Z (s390x) architectures. To successfully start the workspace on these architectures, the only option is to remove this component from the devfile. Alternatively, you can refer to <<using-oc-tool,Using OpenShift CLI tool>> documentation, which describes how to run Open VSX separately without starting a workspace.
27+
====
28+
+
2429
[TIP]
2530
====
2631
The environment, including all necessary commands, is defined in the `.devfile.yaml` file.
@@ -66,6 +71,7 @@ To publish your extensions to Open VSX, update the `extensions.txt` file as need
6671
+
6772
Start any workspace and check the available extensions in the Extensions view of the workspace IDE or by opening the `internal` route in the OpenVSX OpenShift project.
6873

74+
[id="using-oc-tool"]
6975
== Using OpenShift CLI (`oc`) tool
7076

7177
.Prerequisites

0 commit comments

Comments
 (0)