Hacker News Reader

Comment by sytse | Hacker News Reader

I love how Netlify allows you to use the benefits of static site technology (like distributed version control) while allowing for dynamic site functionality like forms. I looked at the documentation for forms https://www.netlify.com/docs/form-handling/#receiving-submis... and it looks very easy.

I can see how people would use Netlify over GitLab. By the way, in GitLab we allow you to test a branch with a review app. In fact for 11.5 we're planning to show you a direct link to the page that changes https://gitlab.com/gitlab-org/gitlab-ce/issues/33418 and someone contributed the option to make the static site that is generate with pages private https://gitlab.com/gitlab-org/gitlab-ce/issues/33422

View on HN

Lots of people use Netlify with GitLab as well. Some using our connection to GitLab and some pushing from GitLab's CI to Netlify via CLI.

Any way we could make the connection with Netlify better? Netlify already added support for GitLab https://www.netlify.com/blog/2016/07/13/gitlab-integration-f...

Maybe a JAMS template?

Yeah, we integrate pretty deeply already. We do have some new flows that could potentially make the story around publishing to Netlify from GitLab cloud seamless from an authentication standpoint, would be happy to brainstorm!

Great, please send an email to kirsten@ our company domain with a link to this comment and we'll discuss.

Off-topic, but can I compliment you/GitLab on a truly useful cookie notification popup? For me, that meets the spirit of the GDPR!

Great to hear!

The one thing I've experienced on this front that was clunky was integration between netlify and self-hosted Gitlab. If y'all could come up for a solution for that (which is prettier than "manual" deploy using webhook), I'd love both of your companies even more than I already do.

I just built a test site with Netlify + GitLab. Why must I give it full access to all of my GitLab repositories? I just want to deploy 1 repo. Seems like that opens up unnecessary possibilities for a security breach.

It's the only option with the current OAuth model, however, we only use the token generated in your web browser, and talk directly to GitLab's API from there. We use the token to add a deploy key and a webhook to the specific repository we're linking to, and after that it's discarded. That way there's no long lived token stored on our end that has access to your whole account.

Awesome. Great workaround. Thanks!

Reply on news.ycombinator.com