update jinja page

This commit is contained in:
gwen 2026-03-27 18:25:53 +01:00
parent 3293800c4c
commit 186a3269d3

View file

@ -125,7 +125,7 @@ will appear.
.. note:: Have a look at the `Jinja website's test section <https://jinja.palletsprojects.com/en/stable/templates/#tests>`_ .. note:: Have a look at the `Jinja website's test section <https://jinja.palletsprojects.com/en/stable/templates/#tests>`_
for a closer look about testing a variable. for a closer look about testing a variable.
But first, let's set our `use_for_https` variable to `false`: .. type-along:: Let's set our `use_for_https` variable to `false`
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_070/config/01/config.yml .. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_070/config/01/config.yml
:language: yaml :language: yaml
@ -173,14 +173,44 @@ We have this output:
┣━━ 📓 SOCKS port: 3128 ┣━━ 📓 SOCKS port: 3128
┗━━ 📓 SOCKS host version used by proxy: v5 ┗━━ 📓 SOCKS host version used by proxy: v5
If we set the `use_for_https` to `true` in the :file:`config.yml` user data file, We can see that the value of the `https_proxy.address` is `https.proxy.net`,
then we launch again the Rougail CLI: that is the value loaded in the :file:`config/01/config.yml` user data file.
.. type-along:: Let's set our `use_for_https` variable to `true`
If we set the `use_for_https` variable to `true` in the :file:`config.yml` user data file
.. raw:: html .. raw:: html
:url: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_070/config/01/cmd_ro.txt :url: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_070/config/02/cmd_ro.txt
:class: terminal :class: terminal
then we have a warning: and we then launch again the Rougail CLI:
.. raw:: html
:url: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_070/config/02/output_ro.html
:class: output
..
Variables:
┣━━ 📓 Configure Proxy Access to the Internet: Manual proxy configuration ◀ loaded from the YAML file "config/02/config.yml" (⏳ No proxy)
┗━━ 📂 Manual proxy configuration
┣━━ 📂 HTTP Proxy
┃ ┣━━ 📓 HTTP address: http.proxy.net ◀ loaded from the YAML file "config/02/config.yml"
┃ ┗━━ 📓 HTTP Port: 3128 ◀ loaded from the YAML file "config/02/config.yml" (⏳ 8080)
┣━━ 📓 Also use this proxy for HTTPS: true ◀ loaded from the YAML file "config/02/config.yml" (⏳ true)
┣━━ 📂 HTTPS Proxy
┃ ┣━━ 📓 HTTPS address: http.proxy.net
┃ ┗━━ 📓 HTTPS port: 3128
┗━━ 📂 SOCKS Proxy
┣━━ 📓 SOCKS address: http.proxy.net
┣━━ 📓 SOCKS port: 3128
┗━━ 📓 SOCKS host version used by proxy: v5
This time we can see that this time the value of the `https_proxy.address` is `http.proxy.net`,
that is the same value as the `https_proxy.address` value, because the `https_proxy.address` variable is hidden.
And in addition notice that we also have a warning:
:: ::
@ -191,8 +221,14 @@ then we have a warning:
so cannot access to "HTTPS address", so cannot access to "HTTPS address",
it will be ignored when loading from the YAML file "config/01/config.yml" it will be ignored when loading from the YAML file "config/01/config.yml"
This warning is an alert. It tells us that the `https_proxy.address` variable is unreachable
(because it is hidden) and that this variable's setting **is not used** in the current :term:`configuration`.
.. type-along:: Launching the Rougail CLI in the :term:`read write mode`
What is interesting here is to launch the Rougail CLI in the :term:`read write mode`: What is interesting here is to launch the Rougail CLI in the :term:`read write mode`:
FIXME
.. code-block:: bash .. code-block:: bash
:class: terminal :class: terminal