03 Feb, 2014
1 commit
30 Jan, 2014
2 commits
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
An architectural overview of GitLab
29 Jan, 2014
3 commits
28 Jan, 2014
4 commits
-
Rewrite how Apache/nginx interacts with precompiled assets.
-
This is to help new admins of GitLab understand what components are involved in making GitLab work.
-
Highlight.Js Replace pygments code highlight with client-side library - highlight.js http://highlightjs.org/
27 Jan, 2014
7 commits
-
Document the stash of changes during the upgrade
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Recommend standard MRI implementation
26 Jan, 2014
1 commit
25 Jan, 2014
3 commits
-
Update installation.md with new git version
-
Database Confusion To prevent https://twitter.com/TechIsCool/status/426133762032676865
24 Jan, 2014
5 commits
-
Release Procedure This should be in line with what is actually happening.
23 Jan, 2014
1 commit
22 Jan, 2014
8 commits
-
Warn Against Version Managers
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
21 Jan, 2014
1 commit
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
20 Jan, 2014
4 commits
-
Explain where the memory recommendation comes from The 250MB repo limit is caused by the git command line. Also see MR !422
-
Encouragement during install
-
This reverts commit a757c4a24f110aa25ad36dd347d499cf859e4d0d. While it is true that Grack memory use while sending data to a client was improved, this does not change the fact that the Git processes running on a GitLab server will use more memory for large repositories.
