4 ms·

This is cool, I'm glad somebody built this! I love netlify but I worry about vendor lock-in.

by paulgb 7y ago

quaffapint 7y ago
Why do you worry about vendor lock-in with netlify? They host static sites, so you are free to go anywhere. Unless you happen to be using their other services which this doesn't address anyway.
- chrisfinazzo 7y ago
  This is my concern in a nutshell, unless someone has a tool that spits out a properly formatted .htaccess so I can migrate my HTTP headers and redirect rules. Netlify's playground is easy to use for setting this up, but I'd also like to have this available in a standard format - just as an escape hatch in case I need it. https://www.htaccessredirect.net https://www.htaccessredirect.net is there, but I'm thinking even less configuration if that's possible.
gk1 7y ago
Netlify doesn’t hold your files; they stay in GitHub or whatever repo you decide to use.
reificator 7y ago
I'm usually paranoid about vendor lock in, but I can't join you on this one. Netlify assumes a version control repository that you can pull from, run a build step, and then host static files from. The build tools are open source, the output is static and trivial to download and rehost, and the repository is git meaning one clone is all you need to port to any other service. Where exactly is the vendor lock in?
- StavrosK 7y ago
  Nowhere (unless you use Netlify-specific features like Lambdas, forms etc). You can just copy your static site elsewhere and you're ready.
- paulgb 7y ago
  It's not so much my code that is locked in, as that netlify has spoiled me by making deployment so streamlined that it would be hard to go back to manual deployment. This gives me another option, which I appreciate. That's all I meant.
  - reificator 7y ago
    Netlify makes things easier, but S3 + Cloudfront + Route53 (Or insert favorite cloud vendor here) for a static site is not that far behind.
holtalanm 7y ago
this doesn't solve vendor lock-in. You're just trading one vendor for another.

This is cool, I'm glad somebody built this! I love netlify but I worry about vendor lock-in.

by paulgb 7y ago

This is cool, I'm glad somebody built this! I love netlify but I worry about vendor lock-in.

Why do you worry about vendor lock-in with netlify? They host static sites, so you are free to go anywhere. Unless you happen to be using their other services which this doesn't address anyway.

chrisfinazzo 7y ago
This is my concern in a nutshell, unless someone has a tool that spits out a properly formatted .htaccess so I can migrate my HTTP headers and redirect rules. Netlify's playground is easy to use for setting this up, but I'd also like to have this available in a standard format - just as an escape hatch in case I need it. https://www.htaccessredirect.net https://www.htaccessredirect.net is there, but I'm thinking even less configuration if that's possible.

gk1 7y ago

Netlify doesn’t hold your files; they stay in GitHub or whatever repo you decide to use.

reificator 7y ago

I'm usually paranoid about vendor lock in, but I can't join you on this one. Netlify assumes a version control repository that you can pull from, run a build step, and then host static files from. The build tools are open source, the output is static and trivial to download and rehost, and the repository is git meaning one clone is all you need to port to any other service. Where exactly is the vendor lock in?

StavrosK 7y ago
Nowhere (unless you use Netlify-specific features like Lambdas, forms etc). You can just copy your static site elsewhere and you're ready.
paulgb 7y ago
It's not so much my code that is locked in, as that netlify has spoiled me by making deployment so streamlined that it would be hard to go back to manual deployment. This gives me another option, which I appreciate. That's all I meant.
- reificator 7y ago
  Netlify makes things easier, but S3 + Cloudfront + Route53 (Or insert favorite cloud vendor here) for a static site is not that far behind.

holtalanm 7y ago

this doesn't solve vendor lock-in. You're just trading one vendor for another.