stove/rougail
3
0
Fork 0
Code Issues 5 Pull requests 1 Projects Releases Wiki Activity

update 2

Browse source
This commit is contained in:
gwen 2026-01-10 09:16:00 +01:00
parent 095f0be622
commit 2cf3b0e752
1 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/tutorial/disabled.rst
View file

@ -374,6 +374,15 @@ Let's introduce a new property here:
- with the `disabled` property, the variables are *deactivated*
- with the `hidden` property, the variables are just not seen when loading the user data.
.. questions:: Question: shall we use the `disabled` property here?
Is it relevant to use the :term:`disabled property <disabled>` here?
**answer**: No! Because we *need* to use these variables at any :term:`context` of the proxy's manual configuration use case,
we simply have to point their values ​​in one direction or another depending on this or that context,
that's why it is absolutely not a question of disabling them. The `manual.https_proxy.address`
and the `manual.http_proxy.port` variables shall not be disabled in the manual mode.
Now we can set a `hidden` property to the `https_proxy` family:
Here is our new :file:`20-manual.yml` structure file:
@ -511,7 +520,7 @@ a `variable` target parameter that points to it: `variable: _.use_for_https`.
.. prerequisites:: Reminder
The underscore and the point before the variable (`_.use_for_https`) points to the variable that lives in the parent
The underscore and the point before the variable (`_.use_for_https`) points to the variable that lives in the same
family.
.. questions:: Question: how does it work?
@ -523,15 +532,6 @@ With this :confval:`use_for_https` boolean variable, there are two possibilities
- The http proxy's configuration will be reused for the https proxy's configuration
- The http proxy's will not be reused for the https proxy's configuration
.. questions:: Question: shall we use the `disabled` property here?
Is it relevant to use the :term:`disabled property <disabled>` here?
**answer**: No! Because we *need* to use these variables at any :term:`context` of the proxy's manual configuration use case,
we simply have to point their values ​​in one direction or another depending on this or that context,
that's why it is absolutely not a question of disabling them. The `manual.https_proxy.address`
and the `manual.http_proxy.port` variables shall not be disabled in the manual mode.
Here is an example with different user values for handling HTTP and HTTPS:
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_053/config/01/config.yml