There is a major problem with this issue because you cannot store databases directly on github. I have found two alternatives to it.
The first one is using Github as "server" in which we do not store data. Rather we would store SQL files. These files would have a all insert statemens to reassemble the database. As time goes by our database is going to be quite huge and reassembling all that data is gonna take some time i guess. So i don't know if this is a valid strategy. MySQL has a tool to export these SQL files. After each pulling we would have to drop and recreate the tables.
Another valid alternative is to find a free database hosting plattform in which the data is stored and each data generating would store the data immediately on the right server under the right conditions. Since we do not have images/videos, the size of the data shouldn't increase by multiple megabytes.
And well the last alternative would be to find a valid datahosting platform which won't be free :).
There is a major problem with this issue because you cannot store databases directly on github. I have found two alternatives to it.
The first one is using Github as "server" in which we do not store data. Rather we would store SQL files. These files would have a all insert statemens to reassemble the database. As time goes by our database is going to be quite huge and reassembling all that data is gonna take some time i guess. So i don't know if this is a valid strategy. MySQL has a tool to export these SQL files. After each pulling we would have to drop and recreate the tables.
Another valid alternative is to find a free database hosting plattform in which the data is stored and each data generating would store the data immediately on the right server under the right conditions. Since we do not have images/videos, the size of the data shouldn't increase by multiple megabytes.
And well the last alternative would be to find a valid datahosting platform which won't be free :).