Update HTTP -> HTTPS (#72244)
Co-authored-by: Ronald Eddy Jr <ron@Ronalds-MacBook-Pro.local>
This commit is contained in:
parent
c9fa1d0e7e
commit
d18901dd4a
5 changed files with 6 additions and 6 deletions
|
@ -6,7 +6,7 @@ Contributing to the Ansible Documentation
|
|||
|
||||
Ansible has a lot of documentation and a small team of writers. Community support helps us keep up with new features, fixes, and changes.
|
||||
|
||||
Improving the documentation is an easy way to make your first contribution to the Ansible project. You do not have to be a programmer, since most of our documentation is written in YAML (module documentation) or `reStructuredText <http://docutils.sourceforge.net/rst.html>`_ (rST). Some collection-level documentation is written in a subset of `Markdown <https://github.com/ansible/ansible/issues/68119#issuecomment-596723053>`_. If you are using Ansible, you already use YAML in your playbooks. rST and Markdown are mostly just text. You do not even need git experience, if you use the ``Edit on GitHub`` option.
|
||||
Improving the documentation is an easy way to make your first contribution to the Ansible project. You do not have to be a programmer, since most of our documentation is written in YAML (module documentation) or `reStructuredText <https://docutils.sourceforge.io/rst.html>`_ (rST). Some collection-level documentation is written in a subset of `Markdown <https://github.com/ansible/ansible/issues/68119#issuecomment-596723053>`_. If you are using Ansible, you already use YAML in your playbooks. rST and Markdown are mostly just text. You do not even need git experience, if you use the ``Edit on GitHub`` option.
|
||||
|
||||
If you find a typo, a broken example, a missing topic, or any other error or omission on this documentation website, let us know. Here are some ways to support Ansible documentation:
|
||||
|
||||
|
|
|
@ -136,7 +136,7 @@ We use:
|
|||
Syntax highlighting - Pygments
|
||||
------------------------------
|
||||
|
||||
The Ansible documentation supports a range of `Pygments lexers <http://pygments.org/>`_
|
||||
The Ansible documentation supports a range of `Pygments lexers <https://pygments.org/>`_
|
||||
for `syntax highlighting <https://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html#code-examples>`_ to make our code examples look good. Each code-block must be correctly indented and surrounded by blank lines.
|
||||
|
||||
The Ansible documentation allows the following values:
|
||||
|
@ -238,7 +238,7 @@ Modules require different suffixes from other plugins:
|
|||
Adding local TOCs
|
||||
^^^^^^^^^^^^^^^^^
|
||||
|
||||
The page you're reading includes a `local TOC <http://docutils.sourceforge.net/docs/ref/rst/directives.html#table-of-contents>`_.
|
||||
The page you're reading includes a `local TOC <https://docutils.sourceforge.io/docs/ref/rst/directives.html#table-of-contents>`_.
|
||||
If you include a local TOC:
|
||||
|
||||
* place it below, not above, the main heading and (optionally) introductory text
|
||||
|
|
|
@ -239,5 +239,5 @@ https://www.reddit.com/r/ansible/comments/gj5a93/trying_to_get_uptime_from_secon
|
|||
Jinja2 filters included with Ansible
|
||||
:doc:`playbooks_tests`
|
||||
Jinja2 tests included with Ansible
|
||||
`Jinja2 Docs <http://jinja.pocoo.org/docs/>`_
|
||||
`Jinja2 Docs <https://jinja.palletsprojects.com/>`_
|
||||
Jinja2 documentation, includes lists for core filters and tests
|
||||
|
|
|
@ -198,7 +198,7 @@ Here's another example, from the same template:
|
|||
This loops over all of the hosts in the group called ``monitoring``, and adds an ACCEPT line for
|
||||
each monitoring hosts' default IPv4 address to the current machine's iptables configuration, so that Nagios can monitor those hosts.
|
||||
|
||||
You can learn a lot more about Jinja2 and its capabilities `here <http://jinja.pocoo.org/docs/>`_, and you
|
||||
You can learn a lot more about Jinja2 and its capabilities `here <https://jinja.palletsprojects.com/>`_, and you
|
||||
can read more about Ansible variables in general in the :ref:`playbooks_variables` section.
|
||||
|
||||
.. _lamp_rolling_upgrade:
|
||||
|
|
|
@ -188,7 +188,7 @@ To reference an IP address from your facts using the dot notation::
|
|||
Transforming variables with Jinja2 filters
|
||||
==========================================
|
||||
|
||||
Jinja2 filters let you transform the value of a variable within a template expression. For example, the ``capitalize`` filter capitalizes any value passed to it; the ``to_yaml`` and ``to_json`` filters change the format of your variable values. Jinja2 includes many `built-in filters <http://jinja.pocoo.org/docs/templates/#builtin-filters>`_ and Ansible supplies many more filters. To find more examples of filters, see :ref:`playbooks_filters`.
|
||||
Jinja2 filters let you transform the value of a variable within a template expression. For example, the ``capitalize`` filter capitalizes any value passed to it; the ``to_yaml`` and ``to_json`` filters change the format of your variable values. Jinja2 includes many `built-in filters <https://jinja.palletsprojects.com/templates/#builtin-filters>`_ and Ansible supplies many more filters. To find more examples of filters, see :ref:`playbooks_filters`.
|
||||
|
||||
.. _setting_variables:
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue