Victor Morales | 6a91997 | 2017-09-28 18:29:54 -0700 | [diff] [blame] | 1 | ======================= |
| 2 | Modify execution values |
| 3 | ======================= |
| 4 | |
| 5 | In order to provide a flexible plataform that adjusts to different developer |
| 6 | needs, it has been implemented two mechanism to configure the execution of this |
| 7 | project. |
| 8 | |
| 9 | Settings configuration file |
| 10 | --------------------------- |
| 11 | |
| 12 | The first mechanism refers to the process to replace default configuration |
| 13 | values through a settings configuration file. This file needs to be placed into |
| 14 | the *./etc* folder and named *settings.yaml*. It must contain the key/pair |
| 15 | configuration values that will be overriden. |
| 16 | |
| 17 | .. note:: |
| 18 | |
| 19 | There are sample files (e. g. settings.yaml.development and |
| 20 | settings.yaml.testing) placed into the *./etc* folder. Their purpose is to |
| 21 | provide a reference of different configurations. |
| 22 | |
| 23 | .. end |
| 24 | |
| 25 | Configuration values: |
| 26 | |
| 27 | +------------------+-------------------+---------------------------------------+ |
| 28 | | Key | Values | Description | |
| 29 | +==================+===================+=======================================+ |
| 30 | | build_image | "True" or "False" | Determines if the Docker image is | |
| 31 | | | | retrieved from public hub or built | |
| 32 | | | | from source code. | |
| 33 | +------------------+-------------------+---------------------------------------+ |
| 34 | | clone_repo | "True" or "False" | Determines if all the source code | |
| 35 | | | | repositories of a given component are | |
| 36 | | | | cloned locally. | |
| 37 | +------------------+-------------------+---------------------------------------+ |
| 38 | | compile_repo | "True" or "False" | Determines if all the source code | |
| 39 | | | | repositories of a given component are | |
| 40 | | | | going to be compiled. | |
| 41 | +------------------+-------------------+---------------------------------------+ |
| 42 | | enable_oparent | "True" or "False" | Determines if the OParent project | |
| 43 | | | | will be used during the maven | |
| 44 | | | | compilation. | |
| 45 | +------------------+-------------------+---------------------------------------+ |
| 46 | | skip_get_images | "True" or "False" | Determines if the process to build or | |
| 47 | | | | retrieve docker images of a given | |
| 48 | | | | component are going to skipped. | |
| 49 | +------------------+-------------------+---------------------------------------+ |
| 50 | | skip_install | "True" or "False" | Determines if the process to start | |
| 51 | | | | the services of a given component | |
| 52 | | | | will be started. | |
| 53 | +------------------+-------------------+---------------------------------------+ |
| 54 | |
| 55 | Parameters |
| 56 | ---------- |
| 57 | |
| 58 | The **skip_get_images** and **skip_install** are the only two configuration |
| 59 | values that can be overriden using *-g* and *-i* respectively by the run scripts |
| 60 | (*./tools/run.sh* and *.\\tools\\Run.ps1*). |
| 61 | |
| 62 | .. note:: |
| 63 | |
| 64 | The script parameters take precendence of the configuration file. |
| 65 | |
| 66 | .. end |
| 67 | |
| 68 | .. code-block:: console |
| 69 | |
| 70 | $ ./tools/run.sh sdc -g |
| 71 | |
| 72 | .. end |
| 73 | |
| 74 | |