Live data from Hacker News

GitLab Pages

pages.gitlab.io

101–110 of 317 posts

Re: GitLab Pages

#101
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.

Re: GitLab Pages

#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.

Re: GitLab Pages

#103

Earlier quoted context omitted.

Just for reference—you can achieve this if you run your site behind CloudFlare. I run my own blog this way.

That's not truly end-to-end encrypted though, right? The server -> CloudFlare goes over HTTP.

That's one option; they also offer strict SSL on both sides of the connection: https://www.cloudflare.com/ssl/ as well as keyless as slig pointed out in another comment.

Re: GitLab Pages

#104
post #8

This is great -- it has a killer feature that I think GitHub Pages is sorely missing (unless it exists and I'm just ignorant to the fact). Custom domains WITH SSL. Right now I have my custom domain set up on GitHub, but it's not SSL. I would love to be able to do that.

Clourfare provides free SSL - just proxy through them.

There are several problems with it:

1. the certificate is not generated by you (in the Free or the Pro plan) but by them and these certificates are for multiple domain names. So you end up sharing your certificate with other domains / websites of dubious nature that are also on CloudFlare's network.

2. CloudFlare only secures the connection between users and the CloudFlare network. It does not secure the connection between CloudFlare and your hosting service, unless your hosting service also supports TLS/SSL connections and you activate their Strict SSL option.

For the purposes of hosting a project website, secure connections are more important than ever due to the potential of external attackers, which could very well be a government institution, to infect distributed binaries or source code. Instances like XcodeGhost will become more common imho. And a secure connection between your user's browser and your hosting server is not 100% secure, but it's a good start. And towards that purpose CloudFlare Free in front of GitHub Pages isn't very good ;-)

Re: GitLab Pages

#105
post #42

Earlier quoted context omitted.

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.

>Save the outrage for people who are actually discriminated against

How about white people at Github?

Re: GitLab Pages

#106
post #21

Earlier quoted context omitted.

Racist attitudes? Interesting - not sure what you're talking about. Could you link a source?

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...

Well granted, they are making an impact.

It might not be the impact they wanted.

It reminds me of how ardent fans of (programing language, framework, brand, etc) are usually its worst enemies. But doing what they are doing, they are working for the opposition in fact.

Re: GitLab Pages

#107

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 .

Same experience here. I use Gitlab for my personal projects and Github for my open-source projects. Hopefully the speed improves soon.

Re: GitLab Pages

#108

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 .

This is the trouble for me using Gitlab.com. Feels like there is a lot of 'n+1' going on in the background. I'm sure there aren't, but it feels like a Rails app that is suffering from that.

Other than that it's great. I've moved nearly everything over from GitHub

Re: GitLab Pages

#109
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.

GitHub Flavored Markdown is itself a rip of the markdown standard. Is it giving enough credit to markdown for GitHub to include the word "markdown" in the name? If so, then by extension it should be sufficient for GitLab to include "flavored markdown" in the name. ;)

Re: GitLab Pages

#110

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.

You can totally use Jekyll plugins since you can define any command in .gitlab-ci.yml. It's like running Jekyll locally.

And custom domain are supported as well. See the bottom of https://pages.gitlab.io

Post reply on HN