I a huge fan of Gitlab and have seen them grow since when I started using them. This is a great new set of features. Looking forward to trying this out!
GitLab Pages
211–220 of 317 posts
Re: GitLab Pages
#212Earlier quoted context omitted.
We have currently no plans, but happy to discuss it [0]. [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/14932
Would love to be able to use my GitHub username on GitLab as well. Currently occupied by a dormant user with zero activity over the last 10 months, no repos except a fork of GitLab CE and no added commits to it. Of course I don't know if he has private repos or not.
Re: GitLab Pages
#213Yes. 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.
We detached this subthread from https://news.ycombinator.com/item?id=11431003 and marked it off-topic.
Re: GitLab Pages
#214Earlier quoted context omitted.
you already made up your mind that [white males] got to where they are unfairly Given the disproportionate amount of power that white males have in America, there are two possibilities. One possibility is that white males really are that superior. We (white males) have the power because we're the best. Conversely, this would also of course imply that other groups like women and minorities are intrinsically inferior.…
> there are two possibilities. Oh no! > The other possibility is that the system really is tilted in the favor of certain groups, and that has affected the distribution of power and wealth that you see in America today Wrong. There is another possibility, which is that once upon a time the system was severely tilted, and for various complex reasons there is a _massive_ multi-generational delay between leveling the sy…
There is another possibility, which is that once upon
a time the system was severely tilted, and for various
complex reasons there is a _massive_ multi-generational
delay between leveling the system seeing the results of
leveling the system.
I think most people would agree that many of the effects of inequality are felt on a multigenerational scale, and that solutions will only fully be realized on a similar time frame. Nobody, even the people making slides at Github, think this can be fixed in an afternoon.What's the functional difference between "living in a system that is severely tilted" and "living in a system that has allegedly been repaired, but in practice will remain tilted for a number of generations until this alleged new-found fairness has a chance to propagate through the system?"
To those affected, I think there would be no useful difference between the two. Long-term solutions do not preclude the need for short-term action.
Consider how difficult and unlikely it is for a low income
white male living in a trailer with, say, alcoholic anti-intellectual
parents to, say, become one of the wealthiest people in the
country.
Absolutely. Odds are definitely stacked against that guy. White males can have any number of horrible problems. And many people of color are born into relatively easy lives.To be clear: nobody is claiming otherwise. Regardless of your feelings about white priviledge, please understand that it does not involve the idea that all things are always easy for all white people.
Re: GitLab Pages
#215Just want to shout out that you can actually get HTTPS on your custom domained Github Page now with Kloudsec[1]. We actually built a dedicated onboarding tool for this: https://kloudsec.com/github-pages [1] Kloudsec is a CDN for programmers
Is the connection between your servers and the GitHub Pages servers unencrypted?
Re: GitLab Pages
#216Earlier 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.
Re: GitLab Pages
#217Re: GitLab Pages
#218Re: GitLab Pages
#219Earlier quoted context omitted.
We detached this subthread from https://news.ycombinator.com/item?id=11431003 and marked it off-topic.
I'm sad to see that. The subject was arguably right on topic. I get the feeling that it was taken down only because it was inconvenient for someone.
It's a tempting feeling to get, and a contagious one, but no—the only inconvenience we care about is that of HN readers who don't want to read tedious flamewars tacked like burning barnacles onto the top comment. I'm kind of glad you said that, though, because usually the sinister implication goes the other way, Gitlab being a YC-funded startup and all.
Speaking of convenience, it's not that inconvenient to scroll down to find the flamewar. Seems like a reasonable balance to me.
Re: GitLab Pages
#220Earlier 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.
This would be an absolute showstopper bug which would prevent some of us from using GitLab Pages if it became a requirement. Definitely do not want.