4 ms·
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 s
by 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 agoNowhere (unless you use Netlify-specific features like Lambdas, forms etc). You can just copy your static site elsewhere and you're ready.
- paulgb 7y agoIt'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 agoNetlify makes things easier, but S3 + Cloudfront + Route53 (Or insert favorite cloud vendor here) for a static site is not that far behind.