此内容没有您所选择的语言版本。

13.2. Cartridge Directory Structure


The required directories of a cartridge must conform to a set structure or the cartridge can fail to function properly. You can add additional directories and files as needed to support the function of your cartridge.
  • Required files must exist for minimal OpenShift Enterprise support of the cartridge.
  • Discretionary files are recommended, but not necessary. For example, conf.d is the standard file where a web framework installs its httpd configuration.
  • Optional files are not necessary. Use optional files to support additional cartridge functionality.

Figure 13.1. Cartridge Directory Structure

To support multiple software versions within one cartridge, create symbolic links between the $cartridge_name/bin/control file and the $cartridge_name/versions/$software_version/bin/control file. Alternatively, use the $cartridge_name/bin/control file as a shim to call the control file for the desired version.
When creating an instance of your cartridge for use by a gear, OpenShift Enterprise copies the files, links, and directories from the cartridge library, with the exception of the $cartridge_name/usr/ directory. The $cartridge_name/usr/ directory is symbolically linked to the gear's cartridge instance. This link enables all cartridge instances to share libraries and other data.
See Chapter 3, Locking Cartridges for details on customizing a cartridge instance.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat