升级OpenShift Data Science Self-managedSelf- managed 1.22 升级 OpenShift Data Science Self-managed 了解如何在 OpenShift Container Platform 上升级 Red Hat OpenShift Data Science Last Updated: 2023-07-03 Red Hat OpenShift Data Science Self-managed 1.22 22 升级 OpenShift Data Science Self-managed 了解如何在 OpenShift Container Platform 上升级 Red Hat OpenShift Data Science 法律通告 法律通告 Copyright © 2023 Red Hat, Inc. The text of and illustrations in this document SCIENCE SELF-MANAGED 概述 概述 第 第 3 章 章 为 为 OPENSHIFT DATA SCIENCE 配置升 配置升级 级策略 策略 3 4 5 目 目录 录 1 Red Hat OpenShift Data Science Self-managed 1.22 升 升级 级 OpenShift Data Science Self-managed 2 第 1 章0 码力 | 9 页 | 101.96 KB | 1 年前3
卸载OpenShift Data Science Self-managedData Science Self- managed 1.27 卸载 OpenShift Data Science Self-managed 使用 OpenShift CLI 从 Red Hat OpenShift Container Platorm 集群中删除 Red Hat OpenShift Data Science Self-managed Last Updated: 2023-06-28 OpenShift Data Science Self-managed 1.27 卸载 OpenShift Data Science Self-managed 使用 OpenShift CLI 从 Red Hat OpenShift Container Platorm 集群中删除 Red Hat OpenShift Data Science Self-managed 法律通告 法律通告 Copyright 摘要 摘要 使用 OpenShift CLI 从 OpenShift Container Platform 集群卸载 Red Hat OpenShift Data Science Self-managed。 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 码力 | 10 页 | 102.65 KB | 1 年前3
Weblate 4.12 用户文档Glossary easify maintaining consistency of the translation. A glossary for each language can be managed on its own, but they are stored together as a single component which helps project admins and multilingual Use this translation button displayed on each line in the Other occurrences tab. You can use 自动化翻译 add-on to automate translating of newly added strings which are already translated in another component case file format you use does not support storing states, you might want to use 将未更改的译文标记为 “需要编辑” add-on to flag unchanged strings as needing editing. 参见: 翻译类型功能, 翻译工作流 1.8.3 直接翻译 这是小型团队最常用的设置,任何人都可以直接翻译。这也是0 码力 | 479 页 | 8.00 MB | 1 年前3
Weblate 4.12 用户文档Glossary easify maintaining consistency of the translation. A glossary for each language can be managed on its own, but they are stored together as a single component which helps project admins and multilingual Use this translation button displayed on each line in the Other occurrences tab. You can use 自动化翻译 add-on to automate translating of newly added strings which are already translated in another component case file format you use does not support storing states, you might want to use 将未更改的译文标记为“需要编辑” add-on to flag unchanged strings as needing editing. 参见 翻译类型功能, 翻译工作流 直接翻译 这是小型团队最常用的设置,任何人都可以直接翻译。这也是0 码力 | 823 页 | 11.12 MB | 1 年前3
Weblate 4.8.1 用户文档Glossary easify maintaining consistency of the translation. A glossary for each language can be managed on its own, but they are stored together as a single component which helps project admins and multilingual horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose0 码力 | 453 页 | 7.80 MB | 1 年前3
Weblate 4.7.2 用户文档Glossary easify maintaining consistency of the translation. A glossary for each language can be managed on its own, but they are stored together as a single component which helps project admins and multilingual horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose0 码力 | 448 页 | 7.73 MB | 1 年前3
Weblate 4.7 用户文档Glossary easify maintaining consistency of the translation. A glossary for each language can be managed on its own, but they are stored together as a single component which helps project admins and multilingual horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose0 码力 | 445 页 | 7.72 MB | 1 年前3
Weblate 4.8 用户文档Glossary easify maintaining consistency of the translation. A glossary for each language can be managed on its own, but they are stored together as a single component which helps project admins and multilingual horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose0 码力 | 452 页 | 7.79 MB | 1 年前3
Weblate 4.7.1 用户文档Glossary easify maintaining consistency of the translation. A glossary for each language can be managed on its own, but they are stored together as a single component which helps project admins and multilingual horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose0 码力 | 447 页 | 7.73 MB | 1 年前3
Weblate 4.9 用户文档Glossary easify maintaining consistency of the translation. A glossary for each language can be managed on its own, but they are stored together as a single component which helps project admins and multilingual horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose0 码力 | 794 页 | 10.99 MB | 1 年前3
共 440 条
- 1
- 2
- 3
- 4
- 5
- 6
- 44













