4 ms·

I moved some static sites to Netlify from S3 because it seemed easier than getting HTTPS working on S3. It certainly was, and I haven't looked back. The automat

by paulgb 9y ago

I moved some static sites to Netlify from S3 because it seemed easier than getting HTTPS working on S3. It certainly was, and I haven't looked back. The automatic generation of a static site from the repo is a killer feature I didn't know I needed until I tried it. Congrats to the team!

ledgerdev 9y ago
Yeah, I loved them too really great service that is forward thinking. They work great for large apps or corporate sites, but for small/personal sites their pricing model doesn't work so well, which I can understand. For instance I needed simple http auth on some directories in a site, and to get that it's $45/month. I ended up with caddy on a $5 digital ocean droplet which automatically sets up and renews the lets encrypt SSL for you. Caddy really is pretty damn nice.
- bobfunk 9y ago
  For small/personal sites the pricing model is "Free". I think that tends to work well :)
  - ledgerdev 9y ago
    Not so much when you need a feature not included in free. And free is always subject to change.
    - bobfunk 9y ago
      The features not included in free are not typically things you can't do without for personal projects (ie, password protection, role based access control, role management for team members, etc...)
      - ledgerdev 9y ago
        Password protection is a pretty basic need and need not cost $45/month. Of course the role/team based stuff for $45/month makes perfect sense because those are only applicable on larger projects.
        michaelmior 9y ago
        I've never found a need for password protection on any of the small personal projects I've worked on. But I guess I could imagine some use cases where that would be nice to have.
    - _fool 9y ago
      disclaimer: I work for Netlify. We've changed pricing models 3 times since I've worked here. Each time we've grandfathered people in at their old pricing level, and the last change also gave away substantially more features for free. Never have we moved someone's cheese from "free" to "not free". I understand that this is still a risk - I'm not promising it will never happen - but we have a killer track record of giving away more, not less, over time, and never have we changed the pricing for an existing site (except to give away enough features that many folks downgraded from paid to free with the last change - and even that was opt-in in case you for some reason wanted to keep paying us :D )
CaveTech 9y ago
HTTPS on S3 is quite easy, only requiring the addition of CloudFront.
- paulgb 9y ago
  It looks like there's quite a bit involved: https://medium.com/@sbuckpesch/setup-aws-s3-static-website-hosting-using-ssl-acm-34d41d32e394 https://medium.com/@sbuckpesch/setup-aws-s3-static-website-h... Sure it's "easy" in the sense that the hardest part is editing some JSON, but with Netlify once the site is set up it's literally one click to provision and apply an SSL cert.

by paulgb 9y ago

ledgerdev 9y ago

Yeah, I loved them too really great service that is forward thinking. They work great for large apps or corporate sites, but for small/personal sites their pricing model doesn't work so well, which I can understand. For instance I needed simple http auth on some directories in a site, and to get that it's $45/month. I ended up with caddy on a $5 digital ocean droplet which automatically sets up and renews the lets encrypt SSL for you. Caddy really is pretty damn nice.

bobfunk 9y ago
For small/personal sites the pricing model is "Free". I think that tends to work well :)
- ledgerdev 9y ago
  Not so much when you need a feature not included in free. And free is always subject to change.
  - bobfunk 9y ago
    The features not included in free are not typically things you can't do without for personal projects (ie, password protection, role based access control, role management for team members, etc...)
    - ledgerdev 9y ago
      Password protection is a pretty basic need and need not cost $45/month. Of course the role/team based stuff for $45/month makes perfect sense because those are only applicable on larger projects.
      - michaelmior 9y ago
        I've never found a need for password protection on any of the small personal projects I've worked on. But I guess I could imagine some use cases where that would be nice to have.
  - _fool 9y ago
    disclaimer: I work for Netlify. We've changed pricing models 3 times since I've worked here. Each time we've grandfathered people in at their old pricing level, and the last change also gave away substantially more features for free. Never have we moved someone's cheese from "free" to "not free". I understand that this is still a risk - I'm not promising it will never happen - but we have a killer track record of giving away more, not less, over time, and never have we changed the pricing for an existing site (except to give away enough features that many folks downgraded from paid to free with the last change - and even that was opt-in in case you for some reason wanted to keep paying us :D )

CaveTech 9y ago

HTTPS on S3 is quite easy, only requiring the addition of CloudFront.

paulgb 9y ago
It looks like there's quite a bit involved: https://medium.com/@sbuckpesch/setup-aws-s3-static-website-hosting-using-ssl-acm-34d41d32e394 https://medium.com/@sbuckpesch/setup-aws-s3-static-website-h... Sure it's "easy" in the sense that the hardest part is editing some JSON, but with Netlify once the site is set up it's literally one click to provision and apply an SSL cert.