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

91–100 of 317 posts

Re: GitLab Pages

#91

Post by schwap »

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?

Re: GitLab Pages

#92

Post by iancarroll »

mynewtb wrote: post #72
sytse wrote: post #54

Earlier quoted context omitted.

We're working on adding Cloudflare in front of GitLab Pages in https://gitlab.com/gitlab-com/operations/issues/75 We don't have a lot of experience yet with DDOS protection so there might be downtime as we learn that. As you can see in the issue we're working to implement protection before we need it but it might not be ready in time nor can it protect against everything.

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

GitLab can just disable that...

Re: GitLab Pages

#93

Post by qznc »

dominotw wrote: post #29

Gitlab is still super slow even compared to young projects like gogs. I know many ppl who shied away for gitlab due to its slowness. If I was them, I would stop all copycat 'me too' features like ci/pages ect and put the resources to making it faster. This is a sign that their features are pritorized by business ppl who want to put features on their slides .

I fear in most cases an impressive feature list wins over speed.

Re: GitLab Pages

#94

Post by revanx_ »

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.

Re: GitLab Pages

#95

Post by the_rosentotter »

mrks_ wrote: post #42
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...

Wow, that tweet is blatantly racist. I'm somewhat surprised that this wasn't made into a bigger deal. Or, if it was, that I somehow missed it.

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

Re: GitLab Pages

#96

Post by djsumdog »

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.

Re: GitLab Pages

#98

Post by the_mitsuhiko »

mynewtb wrote: post #72
sytse wrote: post #54

Earlier quoted context omitted.

We're working on adding Cloudflare in front of GitLab Pages in https://gitlab.com/gitlab-com/operations/issues/75 We don't have a lot of experience yet with DDOS protection so there might be downtime as we learn that. As you can see in the issue we're working to implement protection before we need it but it might not be ready in time nor can it protect against everything.

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

For what it's worth Cloudflare does not do anything different for Tor than for regular IPs. Since those are static pages with most likely not exactly questionable content the use of Tor is probably not all that important anyways that the total number of users that might be affected would be miniscule.

Re: GitLab Pages

#99

Post by biot »

atmosx wrote: post #77
zeeshanm wrote: post #8

Earlier quoted context omitted.

Clourfare provides free SSL - just proxy through them.

But the traffic after cloudflare's proxy is plaintext right? I know CloudFlare has better thing to do than sniffing websites but I don't see the point of installing an SSL certification using clouflare or any other third-party which will handle traffic the way they do. You don't own the certificate, they do.

That's one option; they also offer strict SSL on both sides of the connection: https://www.cloudflare.com/ssl/

Re: GitLab Pages

#100

Post by cyphar »

connorshea wrote: post #59
Spivak wrote: post #50

Earlier quoted context omitted.

Only Gitlab CE is OSS, GitLab EE is "publicly viewable" but neither FOSS/OSS [1]. It's really a shame because I would pay good money to have GitLab EE under a FOSS license. [1] https://about.gitlab.com/license-faq/

Out of curiousity, would you consider GPL Affero sufficiently FOSS?

> Out of curiousity, would you consider GPL Affero sufficiently FOSS?

Of course it's a free software license (although I have my doubts about the enforceability of the Affero sections in the AGPL). GitLab EE is proprietary (even though you can read the source).

Post reply on HN