puppet-apache

  • t3_857221
    了解作者
  • 18.1KB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-05-26 09:01
    上传日期
阿帕奇 欢迎使用您的新模块。 可以在找到所生成零件的简短概述。 下面的README模板提供了一个起点,其中包含有关自述文件中包含哪些信息的详细信息。 目录 描述 简要告诉用户为什么他们可能要使用您的模块。 说明模块的功能以及用户可以解决的问题。 这应该是一个简短的描述,以帮助用户确定您的模块是否是他们想要的。 设置 什么apache会影响OPTIONAL 如果很明显您的模块涉及到什么,则可以跳过此部分。 例如,人们可能会发现您的mysql_instance模块会影响他们MySQL实例。 但是,如果还有更多他们应该知道的地方,这里是要提到的地方: 模块将更改,影响或执行的文件,软件包,服务或操作。 模块自动安装的依赖项。 警告或其他重要提示。 设置要求可选 如果您的模块在设置之前需要任何额外的信息(启用了插件同步,其他模块等),请在此处进行说明。 如果您的最新发行版破坏了兼容
puppet-apache-master.zip
  • puppet-apache-master
  • .travis.yml
    1.1KB
  • manifests
  • init.pp
    43B
  • install.pp
    75B
  • .sync.yml
    274B
  • .pdkignore
    519B
  • data
  • common.yaml
    7B
  • Rakefile
    3.5KB
  • .rubocop.yml
    12KB
  • hiera.yaml
    685B
  • .yardopts
    18B
  • .gitlab-ci.yml
    1.6KB
  • Gemfile
    2.7KB
  • appveyor.yml
    1.1KB
  • .devcontainer
  • Dockerfile
    234B
  • devcontainer.json
    790B
  • metadata.json
    1KB
  • .rspec
    31B
  • spec
  • default_facts.yml
    266B
  • classes
  • apache_spec.rb
    228B
  • install_spec.rb
    237B
  • spec_helper.rb
    1.7KB
  • .puppet-lint.rc
    11B
  • .gitignore
    298B
  • CHANGELOG.md
    146B
  • .fixtures.yml
    223B
  • README.md
    4KB
  • .gitattributes
    62B
  • .vscode
  • extensions.json
    79B
内容介绍
# apache Welcome to your new module. A short overview of the generated parts can be found in the [PDK documentation][1]. The README template below provides a starting point with details about what information to include in your README. ## Table of Contents 1. [Description](#description) 1. [Setup - The basics of getting started with apache](#setup) * [What apache affects](#what-apache-affects) * [Setup requirements](#setup-requirements) * [Beginning with apache](#beginning-with-apache) 1. [Usage - Configuration options and additional functionality](#usage) 1. [Limitations - OS compatibility, etc.](#limitations) 1. [Development - Guide for contributing to the module](#development) ## Description Briefly tell users why they might want to use your module. Explain what your module does and what kind of problems users can solve with it. This should be a fairly short description helps the user decide if your module is what they want. ## Setup ### What apache affects **OPTIONAL** If it's obvious what your module touches, you can skip this section. For example, folks can probably figure out that your mysql_instance module affects their MySQL instances. If there's more that they should know about, though, this is the place to mention: * Files, packages, services, or operations that the module will alter, impact, or execute. * Dependencies that your module automatically installs. * Warnings or other important notices. ### Setup Requirements **OPTIONAL** If your module requires anything extra before setting up (pluginsync enabled, another module, etc.), mention it here. If your most recent release breaks compatibility or requires particular steps for upgrading, you might want to include an additional "Upgrading" section here. ### Beginning with apache The very basic steps needed for a user to get the module up and running. This can include setup steps, if necessary, or it can be an example of the most basic use of the module. ## Usage Include usage examples for common use cases in the **Usage** section. Show your users how to use your module to solve problems, and be sure to include code examples. Include three to five examples of the most important or common tasks a user can accomplish with your module. Show users how to accomplish more complex tasks that involve different types, classes, and functions working in tandem. ## Reference This section is deprecated. Instead, add reference information to your code as Puppet Strings comments, and then use Strings to generate a REFERENCE.md in your module. For details on how to add code comments and generate documentation with Strings, see the [Puppet Strings documentation][2] and [style guide][3]. If you aren't ready to use Strings yet, manually create a REFERENCE.md in the root of your module directory and list out each of your module's classes, defined types, facts, functions, Puppet tasks, task plans, and resource types and providers, along with the parameters for each. For each element (class, defined type, function, and so on), list: * The data type, if applicable. * A description of what the element does. * Valid values, if the data type doesn't make it obvious. * Default value, if any. For example: ``` ### `pet::cat` #### Parameters ##### `meow` Enables vocalization in your cat. Valid options: 'string'. Default: 'medium-loud'. ``` ## Limitations In the Limitations section, list any incompatibilities, known issues, or other warnings. ## Development In the Development section, tell other users the ground rules for contributing to your project and how they should submit their work. ## Release Notes/Contributors/Etc. **Optional** If you aren't using changelog, put your release notes here (though you should consider using changelog). You can also add any additional sections you feel are necessary or important to include here. Please use the `##` header. [1]: https://puppet.com/docs/pdk/latest/pdk_generating_modules.html [2]: https://puppet.com/docs/puppet/latest/puppet_strings.html [3]: https://puppet.com/docs/puppet/latest/puppet_strings_style.html
评论
    相关推荐