Gitlab Social Sciences: Difference between revisions
Jump to navigation
Jump to search
Got rid of setup, configuration, and usage of Git - instead just point to documentation. |
Added draft of FAQ |
||
| Line 69: | Line 69: | ||
Once logged in, there are no further differences. | Once logged in, there are no further differences. | ||
== Setup, Configuration and Usage of Git == | == Setup, Configuration and Usage of Git clients == | ||
For more advanced tasks, you will need a Git installed on your computer | For more advanced tasks, you will need a Git installed on your computer. | ||
There is excellent documentation for this available throughout the Internet, for example https://git-scm.com/documentation or https://docs.gitlab.com/ce/gitlab-basics/README.html. | There is excellent documentation for this available throughout the Internet, for example https://git-scm.com/documentation or https://docs.gitlab.com/ce/gitlab-basics/README.html. | ||
It would make little sense to repeat these here. | It would make little sense to repeat these here. | ||
| Line 77: | Line 77: | ||
Note that for most daily tasks, only about 5 Git operations are necessary to know about. | Note that for most daily tasks, only about 5 Git operations are necessary to know about. | ||
== | == Troubleshooting == | ||
For technical issues you can contact [mailto:gitlab@socsci.ru.nl gitlab@socsci.ru.nl]. | |||
== Frequently asked questions == | |||
=== Who has access to gitlab.socsci.ru.nl? === | |||
Short answer: Anyone from Radboud University, and some people from other universities. | |||
Longer answer: All employees and students of Radboud University have access (with their U-, S-, E- or F-number). | |||
If you log in the first time, a corresponding account will be created. | |||
In addition, you can request accounts for people from other universities, for example to collaborate with them on confidential projects. | |||
See External Users above. | |||
== | === Who can see my project(s) within GitLab? === | ||
Short answer: You decide for each project (if you're the project owner). | |||
Longer answer: GitLab distinguishes read-access within 3 layers, and you can choose for each project individually. | |||
TODO: Explain 3 layers with correct terms. | |||
=== 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/. | |||
Longer answer: Git and GitLab are meant primarily for smaller amounts (Megabytes). | |||
Most features like comparing versions, only make sense with text-based files. | |||
Git keeps track of every single change you make in its history. | |||
It and never really forgets, unless you explicitly tell it to. | |||
That means Git repositories only grow larger, and even if you "delete" things, you can go back and un-delete them. | |||
That's a main feature, you have an "unlimited undo". | |||
But that feature makes also impractical for data - you can't really delete them, comparing versions of them makes little sense, and potentially you later want to invite more people or make the project available to everyone - but then you also would have to share the data since they're in the repository history. | |||
Finally, the server simply has limited capacity. | |||
For all these reasons, for data, use https://data.donders.ru.nl/. | |||
<!-- ==References== | <!-- ==References== | ||