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

111–120 of 317 posts

Re: GitLab Pages

#111

Post by jeremiep »

chatmasta wrote: post #109
jeremiep wrote: post #101

Earlier quoted context omitted.

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

Thats a good point! I did not see it that way.

Re: GitLab Pages

#112

Post by dghughes »

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

Being racist against white people isn't countering racism it's just regular racism.

Neither is going so far to the end of the spectrum i.e. "too PC" isn't the opposite of racism either. Hired just because you're not white? Not really a self-esteem boost.

Being inclusive is what Github should be doing to counter racism without the racist sexist bigoted attitude.

Re: GitLab Pages

#113

Post by mkobit »

chatmasta wrote: post #109
jeremiep wrote: post #101

Earlier quoted context omitted.

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

The many "standards" of Markdown also now include CommonMark [1]. There is also some interesting history as to why it is not named "Standard Markdown".

[1] http://commonmark.org/ [2] https://blog.codinghorror.com/standard-markdown-is-now-commo...

Re: GitLab Pages

#114

Post by jobvandervoort »

langolier wrote: post #110
djsumdog wrote: post #96

Earlier quoted context omitted.

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

In fact, you don't even need to use Jekyll. You can use literally anything you want.

Re: GitLab Pages

#115

Post by tootie »

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.

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.

Re: GitLab Pages

#116

Post by jobvandervoort »

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.

This can easily be avoided by provisioning your own runner. In that case, it'll be isolated for the projects of your choosing.

It's important that we note this, as we do provide free runners for anyone to use on GitLab.com.

Re: GitLab Pages

#117

Post by nikojn »

d33 wrote: post #83
scient wrote: post #80

Earlier quoted context omitted.

Im still amazed how people actually have time for this SJW stuff in the actual real world.

Thought I'd leave it here given that I just googled the term: https://www.urbandictionary.com/define.php?term=SJW

How have you managed to escape it for this long? Seriously, what's your secret please for the love of God let me know

Re: GitLab Pages

#118

Post by jobvandervoort »

therealmarv wrote: post #82
jobvandervoort wrote: post #61

Earlier quoted context omitted.

1. Yes, you can use Pages with private projects 2. No, there are no traffic limits.

thanks for your reply jobvandervoort! Are not you afraid that people will use gitlab as cheap hosting service? So what are the limitations on content I can host there? Policy? Can I use it for commercial usage?

We hope people will use it to host their websites.

You can host almost anything there, excluding illegal content.

Commercial content is fine.

Re: GitLab Pages

#120

Post by jobvandervoort »

meagher wrote: post #81
jobvandervoort wrote: post #60

Earlier quoted context omitted.

Unfortunately, you won't be able to claim a username that is already taken. That would be unfair to other users. GitLab.com is growing fast, but most people should be able to still claim their username. Of course, you always have the option to run your own instance relatively easily [0]. [0]: https://about.gitlab.com/downloads/

GitHub has a policy of releasing dormant usernames, will GitLab do that?

We have currently no plans, but happy to discuss it [0].

[0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/14932

Post reply on HN