151–160 of 187 posts
Having spent the last few days trying to get Cloudfront with Lambda@Edge working, I'm excited to see this. Cloudfront is a mess and clearly Lambda@Edge is "cutting edge" at AWS (where cutting edge means "full of bugs")
Earlier quoted context omitted.
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.
Imagine that I set up/rent a server with apache or nginx pre-configured for mass virtual hosting. For instance, servicea.org and service.org are placed into two separate directories with the same names, respectively. As soon as web pages are uploaded the pages are served. What is the difference between that method and Netlify, aside from the forms function?
It's been a year since I last spoke with Netlify staff [^1]. They weren't super keen on the arguments I raised against using their service given you can host Websites that load in 100-200ms on S3 with CloudFront for pennies a month. If course S3 isn't as push-button as Netlify but it's certainly much more extensible and will probably be around longer. [^1]: https://habd.as/zero-to-http-2-aws-hugo/
Recent site I built hosted on Netlify: https://www.magnoliasmill.com
Earlier quoted context omitted.
Could you elaborate? That would be very helpful, the article doesn't quite detail ...
The end result is the same as hosting on S3 + CloudFront, it just saves you a lot of trouble setting things up, makes things just work, gives you nice features like lambdas, A/B testing, forms, authentication, etc etc for free, and just makes your life super easy. Basically, if you have a repository with your Jekyll (or whatever) site, just add it to Netlify and that's it. It's served, and will automatically update w…
May not be widely known, but a startup named Divshot launched what feels to me now like an identical service to Netlify, just a few years earlier. Existed ~2012-2015. They were acquired by Google and their product was converted into Firebase Hosting. I haven't tried it, though: https://firebase.google.com/docs/hosting/
FYI to any readers: Firebase Hosting has nothing to do with the other Firebase stuff. In fact, I personally dislike their live database quite a bit.
If you want to host a simple static site with HTTPS, Firebase Hosting really makes it incredibly easy. My only complaint is that they don't let you view access logs. Here's the official response [0] from the Firebase team as to why that's the case.
Once you have to do anything more complex I think it's better to use a different service. If you don't want to host anything yourself I've heard positive things about Zeit [1], although I haven't personally used it.
[0] https://stackoverflow.com/questions/29669725/can-i-access-w3...
[1] https://zeit.co/
Replace y with x and shuffle some letters and you have Netflix.
Earlier quoted context omitted.
Is it all that different from hosting on S3 or Firebase or GitHub pages?
It's as difference from that as Dropbox is from mounting an NFS share on your computer.
Earlier quoted context omitted.
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!