We build relationships by editing the models and adding optional details in voyager's BREAD editor.
*[Back to Contents](#Contents)*
## IMPORTANT considerations regarding VERSIONING and Voyager
Voyager offers the possibility to create, modify and delete tables of the database. However, when doing so, there is no versioning/history records of these modifications. Therefore, **DO NOT MODIFY TABLES FROM WITHIN VOYAGER**. Please work exclusively with migrations as described above when creating/modifying tables.
When using voyager to develop MyLabStocks, a number of application functionalities are recorded in tables of the database. For example, BREADs are stored in `data_types` and `data_rows`.
An important consequence of this is that these functionalities are not tracked by git, because we git the code but we will never git the database of course. So, how are we going to keep track of th functionalities stored in the database tables?? This issue is discussed by voyager's developers themselves [here](https://github.com/the-control-group/voyager/issues/1030).
An important consequence of this is that these functionalities are not tracked by git, because we git the code but we will never git the database of course. So, how are we going to keep track of the functionalities stored in the database tables?? This issue is discussed by voyager's developers themselves [here](https://github.com/the-control-group/voyager/issues/1030), where they say that this issue is solved in Voyager version 2.
We propose a solution to this, which is based on [iseed](https://github.com/orangehill/iseed). The idea is simple: we create seeders of the functionality tables, and we git these seeders.
Before upgrading to Voyager v2, we propose a temporary solution to this, which is based on [iseed](https://github.com/orangehill/iseed). The idea is simple: we create seeders of the functionality tables, and we git these seeders.
We therefore ask you to follow the procedure described in this example:
...
...
@@ -103,6 +111,8 @@ So, what happened?
- Your BREADs should be functional as they were prior to your edits on the dev branch.
- Your MENU tables are back to what they were, **but you don't see the changes from the Voyager Menu Builder**. To actualize your pages, click on a menu item that you know is conserved (or create a new menu item if you're not sure) and on the dialog box of this item click on **update**. This will tell Voyager to read again the menus and menuitems tables and your page should now display your actualized menus.
*[Back to Contents](#Contents)*
## Releasing <a name="release"></a>
### Types of release and their branches
...
...
@@ -156,6 +166,8 @@ git merge vZ.Z.Z # change with tag name of the new version
```
- Upgrade a server (a VM machine) dedicated to qualification of stable releases and make a few tests to see if all is ok.
