9 ms·
Think Heroku but just for deploying static assets. You can do something as simple as have a git repo of assets, push it, and you're up and running with SSL, etc
by petercooper 8y ago
Think Heroku but just for deploying static assets. You can do something as simple as have a git repo of assets, push it, and you're up and running with SSL, etc, straight away.
How do you get dynamic? Well, they support a build process so static sites or assets can be built at their end, if that's how you roll. But if you want fully dynamic sites, well, no, you can use their AWS Lambda-powered functions service to help build this out, but you won't be deploying something like a PHP or Rails app to Netlify :-) This limitation opens up a lot of other opportunities to simplify deployment, however.
- vorpalhex 8y agoAnd if your main dynamic features are things like handling forms or an occasional db call on the backend, this isn't a bad approach. It's cheaper and less maintenance generally for a lot of simple cases, but obviously won't apply to all cases equally well.
- virgil_disgr4ce 8y agoDatabases are, in general, the next obvious question for a dynamic app on Netlify. Some solutions can use lambdas, but since a straight-up database is always going to be necessary for certain things, it makes me wonder if they'd roll out a paid database at some point... though that sort of conflicts with their "JAM" "no backend! well somebody else's backend maybe?" selling point
- freebs 8y agoFirebase Cloud Firestore is so nice and they've been working on it for a long time, this would likely not be a good use of their time.