@Obsolesce said in GitLab Now Integrates VS Code Into the Browser:

@stacksofplates said in GitLab Now Integrates VS Code Into the Browser:

@Obsolesce said in GitLab Now Integrates VS Code Into the Browser:

not have the typical shitty editor like GitHub has

Huh? GitHub has VSCode as well for an editor now.

It does? When I hit edit, it uses the shitty editor. I don't see an option for VSCode?

Found it, "open in github.dev" does it. I never tried that option, but also it's rare I ever edit in the web browser.

Oh I never did that method. I just hit the period button and it opens.

To be clear, GitLab uses Unleash for their feature flags which is open source. It also has it's own UI, but it's nice to have it in your code base and not need to run a separate server.

@flaxking said in GitLab install on CentOS using Salt:

The Azure CentOS image I used for testing didn't have firewalld enabled by default

Well a, very, old version of CentOS minimal had that issue natively. Maybe that is what Azure built on.

So forget my comments. It turned out maybe your instructions are fine. (Maybe, maybe not. I don't know, but will reinstall using your instructions again just to verify.) My problem was that I was opening up the firewall ports in the wrong zone. The default Install I used made only 1 zone on the master called "FedoraServer." Opening ports on this zone solved the issue. See this post from this morning: https://mangolassi.it/topic/15620/salt-stack-communication-issues/2

@tim_g
Do you know what tools and scripts that is available when installing hyperv-tools?

It just came up.

GitLab, you so funny.
.
.
.
.
.
That was one expensive joke.

That was interesting. Any word on the final status? How much was lost?

If ever there was an RGE*, this would be it.
 
 
 
 
*Resume Generating Event

@stacksofplates said in Proposed server purchase for GitLab.com:

Omg I missed this absurdity from the original article:

We are also attempting to move GitLab application servers and supporting services (e.g. PostgreSQL) to bare metal.

Yeah, out of their minds.

@dafyre said:

@JaredBusch said:

@dafyre said:

As a matter of correctness... Do you have EPEL /REMI or any other repos installed in your CentOS 7 image?

The script is connecting the Gitlab RPM, that is all. The base image he uses for all of these is CentOS 7 minimal, release 1511 unless he has changed the base template on his scale cluster.

Right. I'm just curious if he has added the epel-release or any other repos to it.

Definitely no EPEL. I often use it, but avoid it in the base image.

*runs off to update Gitlab.