Max/zkldi_Tachi
1
0
Fork 0
mirror of https://github.com/zkldi/Tachi.git synced 2026-10-01 03:18:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: update stale dbseeds info

Browse Source
This commit is contained in:
zkldi
2022-09-20 02:42:32 +01:00
parent 000f8969fe
commit 33ad5d5d5f
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs/tachi-server/infrastructure/database-seeds.md
+3 -3
View File
@@ -1,6 +1,6 @@
# Database Seeds
Tachi uses a separate git repository called the [Database Seeds](https://github.com/TNG-dev/Tachi/tree/staging/database-seeds) to maintain 'static' databases.
Tachi tracks the contents of its songs and charts in something called the [Database Seeds](https://github.com/TNG-dev/Tachi/tree/staging/database-seeds).
The databases in question aren't (normally) altered by the server code. We essentially overload git and its CI tools to version control parts of our database.
@@ -12,9 +12,9 @@ They also include all Folder Documents, Table Documents and BMS Course Documents
## Synchronisation
When pushes are made to `develop` (the main branch), our running staging servers will automatically update to that new bit of data.
When pushes are made to `staging` (the main branch), our running staging servers will automatically update to that new bit of data.
When pushes are made to `production`, our running *production* servers will automatically update in the same way.
When pushes are made to `release/2.X`, our running *production* servers will automatically update in the same way.
## Why bother?