docs(tutorial): namespaces
add multiple namespaces foxyproxy use case
This commit is contained in:
parent
f134e96257
commit
26362769ac
1 changed files with 30 additions and 2 deletions
|
|
@ -134,9 +134,37 @@ New "FoxyProxy" namespace
|
||||||
|
|
||||||
git switch --detach 1.1_181
|
git switch --detach 1.1_181
|
||||||
|
|
||||||
Variables related to the Foxy Proxy plugin will be stored in a separate namespaces.
|
|
||||||
|
|
||||||
.. image:: images/foxyproxy.png
|
.. image:: images/foxyproxy.png
|
||||||
|
|
||||||
|
We can see in the FoxyProxy widget that it is possible to add as many proxies as needed.
|
||||||
|
|
||||||
|
So our use case enables us to handle variables related to the Foxy Proxy plugin
|
||||||
|
that should be stored in a separate namespace.
|
||||||
|
|
||||||
|
.. type-along:: Handling multiple namespaces
|
||||||
|
|
||||||
|
It is perfectly possible to define multiple namespaces with Rougail.
|
||||||
|
In the Rougail CLI, the `-s` option is reserved for the main namespace.
|
||||||
|
If we need to add a namespace named FoxyProxy, we must use the `-xn FoxyProxy` option.
|
||||||
|
However, we also need to specify the parameter that indicates the location
|
||||||
|
of the structure files corresponding to this namespace.
|
||||||
|
The `-xd 0 foxyproxy/` option is used to specify the relevant file or folder,
|
||||||
|
here, the :file:`foxyproxy` folder:
|
||||||
|
|
||||||
|
.. raw:: html
|
||||||
|
:class: terminal
|
||||||
|
:url: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_181/config/01/cmd_ro.txt
|
||||||
|
|
||||||
|
..
|
||||||
|
rougail -m firefox/ -s Firefox -xn FoxyProxy -xd 0 foxyproxy/ --types types/proxy --modes_level basic standard advanced -u yaml -yf config/01/config.yml
|
||||||
|
|
||||||
|
The additional namespace is therefore specified via the two command-line options:
|
||||||
|
|
||||||
|
.. code-block:: shell
|
||||||
|
|
||||||
|
-xn FoxyProxy -xd 0 foxyproxy/
|
||||||
|
|
||||||
|
.. keypoints:: let's review the key points
|
||||||
|
|
||||||
|
We learned how to create a namespace for our use case, and even how to use
|
||||||
|
multiple namespaces—that is, how to implement several logical separations.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue