Hacker News new | ask | show | jobs
by pfg 4892 days ago
Agreed. It was also eating a lot of memory.

Upgrade (4.0 -> 4.1) ran smoothly. Only thing that was missing in the upgrade guide was installing a new version of the post-receive hook, but since gitlab:check mentioned that and even provided the command to fix this, it wasn't a problem.

1 comments

gitlab:check is doing a great job at keeping the insanity of the gitlab pace at bay. I started pre-2.0 and have had to go through some hard upgrade steps (just recently went from 3.1 to 4.1 and had to move sqlite to mysql).