Ah nice, I’ve always sort of wondered why this did not exist. It would probably be wise for Gitlab to officially support something like this.
Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
11–20 of 76 posts
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#12My 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.
And Gitea is usable when running on a Raspberry Pi
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#13My 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.
64 GB on a 16 core machine that has nothing else to do.
If any, I think this is maybe too much, every worker just spawns more and more workers. I restricted Postgres from taking all RAM, Sidekiq and Puma to low numbers. But there are more..
I follow the instructions straight from Gitlab.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#14My 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.
Disabling automatic repository housekeeping might help. It can use lots of RAM for large repositories like the Linux kernel.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#15My 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`.
That was a theory I had: That Unicorn leaks and that Unicorn Killer is not killing any of the workers, since it does so all 160 requests and there are no request happening at the moment.
Then I saw the new installation uses Puma ;)
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#16My 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.
That isn't my experience. I installed gitlab on a local debian server and it has been running for 3 months straight now.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#17Hosted 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 maintain a bunch of docker images that are purposed to run on gitlab ci, they are obviously hosted on github because only github has push-event integrations with docker hub.
I make a push, docker hub builds and publishes the image, the image is only pulled by gitlab ci.
Gitlab is great, but it lacks many popular integrations that must come from not-gitlab.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#18For anyone interested, there‘s a similar CLI for GitHub: https://github.com/cli/cli
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#19For anyone interested, there‘s a similar CLI for GitHub: https://github.com/cli/cli
Actually it's quite a shame for the Gitlab team that they don't offer a similar official CLI. The gitlab software is high quality in general, and obviously it's doable by a third party to implement such a tool.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#20My 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.
So what's the reason for crashing? What's the configuration that you change? I assume it's not random trial and error.