Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

github.com

Post reply on HN
Print view View original

1–10 of 76 posts

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#3

Post by kanobo »

mosselman wrote: post #2

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

Hugely ironic, but not surprising since projects on GitHub get better exposure and also the ability to raise funds with GitHub sponsors.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#4

Post by ianbooker »

My new hobby is installing vanilla Gitlab CE on a vanilla server and waiting until it crashes the whole thing. Takes something between 8 to 36 hours.

The server is completely gone, no ping, no ssh. It takes frantic remote power button pushes to even turn it off.

Afterwards I reconfigure various config lines and repeat.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#5

Post by mattl »

ianbooker wrote: post #4

My new hobby is installing vanilla Gitlab CE on a vanilla server and waiting until it crashes the whole thing. Takes something between 8 to 36 hours. The server is completely gone, no ping, no ssh. It takes frantic remote power button pushes to even turn it off. Afterwards I reconfigure various config lines and repeat.

How much RAM? Are you installing from Omnibus packages? I ask because I have two servers and have near perfect uptime.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#6

Post by P4wl0w »

kanobo wrote: post #3
mosselman wrote: post #2

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

Hugely ironic, but not surprising since projects on GitHub get better exposure and also the ability to raise funds with GitHub sponsors.

This is true and important. But I also have to admit that I like the interface of GH more and I am just used to searching on GH - it always has been like google search for code for me.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#7

Post by Jugurtha »

ianbooker wrote: post #4

My new hobby is installing vanilla Gitlab CE on a vanilla server and waiting until it crashes the whole thing. Takes something between 8 to 36 hours. The server is completely gone, no ping, no ssh. It takes frantic remote power button pushes to even turn it off. Afterwards I reconfigure various config lines and repeat.

I have somewhat similar experience. I have 16GB of RAM, 12 CPU.

You can reduce the number of unicorn workers in `config/gitlab.rb`.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#8

Post by gru »

mosselman wrote: post #2

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

I have created a small tool that automatically mirrors public repos from GitLab to GitHub: https://github.com/grdl/gitlab-mirror-maker

Meaning, a repo can be hosted on GL but still benefit from better exposure and disoverability of GH.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#9

Post by lbotos »

Jugurtha wrote: post #7
ianbooker wrote: post #4

My new hobby is installing vanilla Gitlab CE on a vanilla server and waiting until it crashes the whole thing. Takes something between 8 to 36 hours. The server is completely gone, no ping, no ssh. It takes frantic remote power button pushes to even turn it off. Afterwards I reconfigure various config lines and repeat.

I have somewhat similar experience. I have 16GB of RAM, 12 CPU. You can reduce the number of unicorn workers in `config/gitlab.rb`.

what are you seeing in the logs? OOM-killer? Also, newer versions use Puma which lower RAM needs if you are seeing Unicorn OOM Killer
Post reply on HN