3 ms·
If you just want to try it out, the easiest is often Gitlab Development Kit. gem install gitlab-development-kit gdk init cd gitlab-development-kit
by andrelaszlo 7y ago
If you just want to try it out, the easiest is often Gitlab Development Kit.
gem install gitlab-development-kit
gdk init
cd gitlab-development-kit
gdk run
I doubt it will work today though; it's probably pulling everything from Gitlab.
For Docker, check out https://hub.docker.com/r/gitlab/gitlab-ce https://hub.docker.com/r/gitlab/gitlab-ce I haven't tried it out for myself but it seems popular :)
- leipert 7y agoThe GDK installation has changed a bit (just set it up today, you need to run gdk install and gdk start (instead of run) for example). Please also note that it involves installing dependencies on your local machine, like e.g. Ruby / Postgres, etc. Here is the link to the GDK: https://gitlab.com/gitlab-org/gitlab-development-kit https://gitlab.com/gitlab-org/gitlab-development-kit Otherwise I would try the docker container OR just install it with omnibus in a VM: https://about.gitlab.com/install/ https://about.gitlab.com/install/
- andrelaszlo 7y agoOh, thanks. I got that from some old notes since my bookmark didn't work for some reason ;) For me, running Gitlab locally is extremely heavy (webpack especially). How beefy is your computer, as a Gitlab developer?
- leipert 7y agoI have got a 16 GB MacBook from 2018. Funny that you mention Webpack, I am part of the webpack working group and we are trying to improve developer experience: https://about.gitlab.com/company/team/structure/working-groups/webpack/ https://about.gitlab.com/company/team/structure/working-grou... We were able to reduce memory consumption quite a bit, but we are working on different other improvements.
- andrelaszlo 7y agoGreat! I see you were actually involved in one of the problems that bit me (8 GB...). https://gitlab.com/gitlab-org/gitlab-development-kit/issues/458 https://gitlab.com/gitlab-org/gitlab-development-kit/issues/... Small world :)