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

GitLab Pages

pages.gitlab.io

Post reply on HN
Print view View original

131–140 of 317 posts

Re: GitLab Pages

#131

Post by josteink »

mclovinit wrote: post #76
someonenewer wrote: post #36

Earlier quoted context omitted.

Their new 'social impact team' isn't a fan of white people https://twitter.com/_danilo/status/690601512813367297 http://www.breitbart.com/tech/2016/02/08/report-anti-white-a...

geez. i hadn't seen that tweet. crazy. i would love to consider gitlab as an alternative. need to plan on migrating my repos and gists over first. i can't support that type of culture. not today. not ever.

Gitlab has migration tools for most of your github thingies (wikis, issues, prs, etc).

You should be able to migrate quite easily without losing too much history.

http://doc.gitlab.com/ee/workflow/importing/import_projects_...

Re: GitLab Pages

#132

Post by ceejayoz »

eugeneionesco wrote: post #105
the_rosentotter wrote: post #95

Earlier quoted context omitted.

This is the world's smallest violin, playing just for the white people. Save the outrage for people who are actually discriminated against.

>Save the outrage for people who are actually discriminated against How about white people at Github?

Is there any indication they're suffering actual discrimination? Pay gaps, harassment, disproportionately not-hired or fired?

Re: GitLab Pages

#133

Post by langolier »

aviraldg wrote: post #102

> GitLab Runners do not offer secure isolation between projects that they do builds for. You are TRUSTING all GitLab users who can push code to project A, B or C to run shell scripts on the machine hosting runner X. Not sure this sounds like the best idea.

Well, there is an issue for that[0]. Also, as of today[1], all shared Runners on GitLab.com are each on their own VM inside Docker containers, so that message does not apply for sure.

[0] https://gitlab.com/gitlab-org/gitlab-ce/issues/14732 [1] https://about.gitlab.com/2016/04/05/shared-runners/

Re: GitLab Pages

#134

Post by kpcyrd »

djsumdog wrote: post #96
scott_hardy wrote: post #16

I especially like that they have added configuration options to the .gitlab-ci.yml. If I am not mistaken, this means your project can auto-deploy using an arbitrary build process. Here's what an example .gitlab-ci.yml looks like with a GitLab Pages build configuration: https://gitlab.com/pages/pages.gitlab.io/blob/master/.gitlab... A couple friends and I made something similar for GitHub Pages using Travis CI as our…

One of the big limitations of Jekyll + Github pages is you cannot use plugins..any plugins at all. If Gitlab's build process allowed for Jekyll plugins and custom domains, I may consider moving my pages there as well.

jekyll plugins are disabled for a good reason, otherwise you could basically execute anything you want on their server.

Re: GitLab Pages

#135

Post by [deleted] »

revanx_ wrote: post #94
TheLogothete wrote: post #17

Yes. I lobbied several companies to terminate their enterpise contracts with github because of their racist attitudes. All switched within 2 weeks. Some to VS Team Services, some to Gitlab. My work projects went to MSFT, but I think I will transfer my side projects to gitlab from bitbucket, since they have pages now.

I remember when github adopted the Code of Conduct, it was a clear sign for me that it was time to switch. All they need now is the equivalent of Twitter's "Safety Council" to complete the SJW combo.

[deleted]

Re: GitLab Pages

#136

Post by whorleater »

schwap wrote: post #91
iBotPeaches wrote: post #27

Still looks like GitLab EE only :(

I thought that, too. But on the other hand if you're running your own private instance what's really the point of serving up statically generated pages from GitLab instead of just directly off your own HTTP server of choice?

There's less stuff to manage if you're serving up pages from a selfhosted Gitlab instance than actually serving up the repo directly.

Re: GitLab Pages

#137

Post by sytse »

jeremiep wrote: post #101
Trundle wrote: post #6

Dear lord these guys are putting in work. I'm not exactly a huge supporter of Github (the company not the product) so I'm very glad to see it. I look forward to their continued growth.

Yeah, but I wish they'd give more credit where due. On their markdown page they claim "For GitLab we developed something we call "GitLab Flavored Markdown" (GFM)." while that is obviously a ripoff of GitHub Flavoured Markdown.

I agree we should give attribution here and created https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3546 to do so. Edit: this was merged.

Re: GitLab Pages

#138

Post by ZenoArrow »

djsumdog wrote: post #89
ZenoArrow wrote: post #65

Earlier quoted context omitted.

Can you change your username please. HN isn't Reddit.

What's wrong with that person's username?

1. Requesting pictures of boobs is crass.

2. You can't PM people in HN, so it makes no sense.

I can see I got downvoted for suggesting it but I still stand by what I said. I didn't downvote the poster, I was just suggesting they reconsider.

Re: GitLab Pages

#139

Post by sooheon »

gpm wrote: post #127
tootie wrote: post #115

Earlier quoted context omitted.

They should have just had the Code of Conduct from day 1 and not waited until they had an incident to overreact to. I've worked for many places with Codes of Conduct and diversity programs and they are usually run pretty well and are not heavy-handed or staffed with exuberant amateurs. There are proven benefits and established best practices to get it done.

The problem isn't with codes of conduct in the abstract, but with the specific code of conduct that GitHub used. It explicitly permits racism, sexism, and cisphobia as long as they aren't against the wrong groups: > Our open source community prioritizes marginalized people’s safety over privileged people’s comfort. We will not act on complaints regarding: > > ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexi…

This reads like a parody. An actual successful company thought this deserved codifying?

Re: GitLab Pages

#140

Post by sytse »

iancarroll wrote: post #92
mynewtb wrote: post #72

Earlier quoted context omitted.

Please do not use Cloudflare. Their 'protection' against privacy aware Tor users makes accessing sites through incredibly painful.

GitLab can just disable that...

Good idea, I made a note in https://gitlab.com/gitlab-com/operations/issues/75#note_4599...
Post reply on HN