Gitlab Social Sciences: Difference between revisions
Jump to navigation
Jump to search
Mention option to use LFS. |
|||
| Line 95: | Line 95: | ||
=== What can/should be stored on GitLab? === | === What can/should be stored on GitLab? === | ||
Short answer: Scripts, documentation, theses, figures etc. '''No data please!''' For data, use https://data.donders.ru.nl/. | Short answer: Scripts, documentation, theses, figures etc. '''No research data please!''' For research data, use https://data.donders.ru.nl/. | ||
For some niche cases, GitLab's Large File Storage (LFS) might be useful, see below. | |||
Longer answer: Git and GitLab are meant primarily for smaller amounts of data (think Megabytes, not Gigabytes). | Longer answer: Git and GitLab are meant primarily for smaller amounts of data (think Megabytes, not Gigabytes). | ||
Most features, like comparing versions, only really make sense with text-based files. | Most features, like comparing versions, only really make sense with changing text-based files. | ||
Git keeps track of every change you make in its history, and never really | Git keeps track of every change you make in its history, and thus content is never really deleted. | ||
That means Git repositories only grow larger, and even if you "delete" files, you can go back and un-delete them. | That means Git repositories only grow larger, and even if you "delete" files, you can go back and un-delete them. | ||
That's a main feature, you get an "unlimited undo" for all kinds of files (and across different editors and computers). | That's a main feature, you get an "unlimited undo" for all kinds of files (and across different editors and computers). | ||
Keeping an unchangeable history makes it impractical for data - you can't really delete them, comparing versions of them makes little sense. | Keeping an unchangeable history makes it impractical for binary data - you can't really delete them, comparing versions of them makes little sense. | ||
And potentially you later want to make the project available to more people - but maybe without sharing all data. | And potentially you later want to make the project available to more people - but maybe without sharing all data. | ||
For these reasons, please use https://data.donders.ru.nl/ for your research data. | |||
For | |||
In case you need certain large data files for your development, GitLab offers Large File Storage (LFS). | |||
Please only use this feature after careful consideration, for files that are integral to your project and for which no other data repository makes sense. | |||
Note that you need to install the LFS extension on your local machine to use this. | |||
For more documentation, please refer to https://docs.gitlab.com/ce/workflow/lfs/manage_large_binaries_with_git_lfs.html. | |||
=== What happens to my GitLab projects when I leave? === | === What happens to my GitLab projects when I leave? === | ||