91–100 of 187 posts
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?
Could someone enlighten me how does Netlify differ from Github pages? If I want to put up a static website, what's the advantage of using Netlify over Github pages?
The main difference for me seems to be netlify let's you have input forms and do POST requests whereas github pages is more static and only serves static pages via GET.
How is an "Application Delivery Network" different from a CDN (which AFAIK is what Netlify currently is)? Netlify still only handles static content, right?
I use Netlify for all my static sites and it's been amazing. All I have to do is push and they take care of everything else, I can't understate how much I love the product. If you want to check out a live deployment, my website https://www.stavros.io/ is on Netlify. I especially like how they provide forms, lambdas and very easy testing by just pushing to another git branch. I don't see why anyone would use Github/Gi…
This is critical for me since I edit using my Android Jekyll-optimized tool Teddy Hyde (https://play.google.com/store/apps/details?id=com.EditorHyde...).
I use Netlify for all my static sites and it's been amazing. All I have to do is push and they take care of everything else, I can't understate how much I love the product. If you want to check out a live deployment, my website https://www.stavros.io/ is on Netlify. I especially like how they provide forms, lambdas and very easy testing by just pushing to another git branch. I don't see why anyone would use Github/Gi…
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.…
I use Netlify for all my static sites and it's been amazing. All I have to do is push and they take care of everything else, I can't understate how much I love the product. If you want to check out a live deployment, my website https://www.stavros.io/ is on Netlify. I especially like how they provide forms, lambdas and very easy testing by just pushing to another git branch. I don't see why anyone would use Github/Gi…
Can you edit (say Jekyll blogs) on GitHub and them somehow push to Netlify automatically? This is critical for me since I edit using my Android Jekyll-optimized tool Teddy Hyde ( https://play.google.com/store/apps/details?id=com.EditorHyde... ).
I use Netlify for all my static sites and it's been amazing. All I have to do is push and they take care of everything else, I can't understate how much I love the product. If you want to check out a live deployment, my website https://www.stavros.io/ is on Netlify. I especially like how they provide forms, lambdas and very easy testing by just pushing to another git branch. I don't see why anyone would use Github/Gi…
Is it all that different from hosting on S3 or Firebase or GitHub pages?
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/
I use Firebase hosting for a static site that gets between 100-400gb of traffic per month, and it works out a bit cheaper than Netlify ($15-$50/m vs. flat $45/m). I hardly ever use their web interface and just deal with their one line CLI. My biggest concern with Firebase is if it's still going to be around in a year or two. That's why I'd be reluctant to use it for DB and auth stuff. I narrowly avoided jumping into…
Earlier quoted context omitted.
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.…
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.
Maybe a JAMS template?