domain name ok
This commit is contained in:
parent
0a10dfbd7d
commit
01d99cbd01
1 changed files with 9 additions and 11 deletions
|
|
@ -286,12 +286,11 @@ A variable with type `port`
|
||||||
|
|
||||||
git switch --detach v1.1_032
|
git switch --detach v1.1_032
|
||||||
|
|
||||||
|
After the `address` variable let's add, according to our use case, a new variable of type `port`:
|
||||||
After the `address` variable let's add, according to our use case,
|
|
||||||
|
|
||||||
.. image:: images/firefox_port.png
|
.. image:: images/firefox_port.png
|
||||||
|
|
||||||
a new variable of type `port`. Our structure file looks like this:
|
Our structure file looks like this:
|
||||||
|
|
||||||
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/tag/v1.1_032/firefox/10-manual.yml
|
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/tag/v1.1_032/firefox/10-manual.yml
|
||||||
:language: yaml
|
:language: yaml
|
||||||
|
|
@ -305,7 +304,7 @@ a new variable of type `port`. Our structure file looks like this:
|
||||||
|
|
||||||
:tutorial:`Download this file from the rougail-tutorials git repository <src/tag/v1.1_032/firefox/10-manual.yml>`
|
:tutorial:`Download this file from the rougail-tutorials git repository <src/tag/v1.1_032/firefox/10-manual.yml>`
|
||||||
|
|
||||||
Let's assing a value to this port:
|
Let's assign a value to this port:
|
||||||
|
|
||||||
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_032/config/02/config.yml
|
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_032/config/02/config.yml
|
||||||
:language: yaml
|
:language: yaml
|
||||||
|
|
@ -350,13 +349,7 @@ We have this output:
|
||||||
|
|
||||||
How can we know what validations the port type performs on the value assigned to the variable?
|
How can we know what validations the port type performs on the value assigned to the variable?
|
||||||
|
|
||||||
There are a number of validations that are carried out with this `port` type:
|
There are a number of validations that are carried out with this `port` type.
|
||||||
|
|
||||||
- well-known ports (1 to 1023) are allowed
|
|
||||||
- registred ports (1024 to 49151) are allowed
|
|
||||||
|
|
||||||
.. - private ports (greater than 49152) are allowed
|
|
||||||
|
|
||||||
Now let's assign a value that is outside the allowed ports:
|
Now let's assign a value that is outside the allowed ports:
|
||||||
|
|
||||||
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_032/config/03/config.yml
|
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/commit/v1.1_032/config/03/config.yml
|
||||||
|
|
@ -424,6 +417,11 @@ Let's add one more variable in the `manual` family, with a much more basic type:
|
||||||
- we have decided to create a new structure file :file:`firefox/20-manual.yml`.
|
- we have decided to create a new structure file :file:`firefox/20-manual.yml`.
|
||||||
This is not necessary but usefull, please have a look at the :ref:`structure file organization and naming conventions <namingconvention>`
|
This is not necessary but usefull, please have a look at the :ref:`structure file organization and naming conventions <namingconvention>`
|
||||||
|
|
||||||
|
- here we reuse the `manual` existing family name that has already been declared in the :file:`firefox/10-manual.yml` structure file.
|
||||||
|
The content in the :file:`firefox/20-manual.yml` will be added to the existing `manual` family.
|
||||||
|
Note that if two different structure files are loaded by Rougail and if they declare the same family name,
|
||||||
|
then **the declarations are concatenated in the family name**.
|
||||||
|
|
||||||
Let's switch this boolean variable to a `false` value:
|
Let's switch this boolean variable to a `false` value:
|
||||||
|
|
||||||
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/tag/v1.1_033/config/02/config.yml
|
.. extinclude:: https://forge.cloud.silique.fr/stove/rougail-tutorials/raw/tag/v1.1_033/config/02/config.yml
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue