@_phzn @philnash @Herschel_R @DKundel @Netlify @glitch @jsunconf @jekyllrb Very. You can do all of this on the free plan (and much besides).
The number of free form submissions each month is limited, but scales elastically. The limit on monthly bandwidth is so high you'd need to be a *beast* to reach it.
Hooks, notifications, rollbacks etc - all free.
@philnash @Herschel_R @DKundel @Netlify @glitch @jsunconf I'd venture these as a start (available on @Netlify, but not GH Pages, AFAIK):
➡️ Free, auto-renewing certs for https
➡️ Support for @jekyllrb plugins
➡️ Support for any SSG you prefer
➡️ Integrated form handling
➡️ Preview builds from pull requests
➡️ Free, auto-renewing certs for https
➡️ Support for @jekyllrb plugins
➡️ Support for any SSG you prefer
➡️ Integrated form handling
➡️ Preview builds from pull requests
@jaffathecake Probably won't put in an offer, but it certainly is time to binge my way through ALL of Spaced again.
@kylemathews @chrisbiscardi @oliverturner @Netlify @VeryThorough Cool. Curious though: do you rebuild all sites no matter which one has received code changes? Or are you doing something crafty?
@chrisbiscardi @JeremyMorrell @Netlify The tricky bit is that every site in that monorepo would share and be triggered to rebuild by the same git hook. So all sites would rebuild no matter which one changed.
Maybe the build script of each site could test git logs to see if files in its scope where part of the commit?
Maybe the build script of each site could test git logs to see if files in its scope where part of the commit?
@stefanjudis @nuxt_js @contentful @Netlify You are safe to play with this. The only thing you can hurt is your own deploy. It is not advertised widely due to the complexity inherent in managing your own caching mechanics, which would likely generate a lot of support requests from people getting unexpected deploy results.
@stefanjudis @nuxt_js @contentful @Netlify I recently discovered this undocumented ability, which may be useful!
See the gulp file for where the build cache gets used.
Difficulty comes in managing your caching. Netlify can't help you there, so you'd be on your own if you need to debug it.
https://github.com/philhawksworth/content-shards
See the gulp file for where the build cache gets used.
Difficulty comes in managing your caching. Netlify can't help you there, so you'd be on your own if you need to debug it.
https://github.com/philhawksworth/content-shards
@Jack_RedCat @thekitze It depends on what you mean by "finish". Even after many dozens of hours researching, writing, designing, and practicing a talk, I don't consider it finished. Final fine-tuning is standard.
The only reasons to need it advance are trust or preloading for display. Neither is good.
The only reasons to need it advance are trust or preloading for display. Neither is good.
@alexnmoldovan @Jack_RedCat @thekitze Even if I've given a talk before, I don't like to "freeze" it by sending slides in advance. The ability to tune it during final run-throughs (often the night before), or update with latest info is crucial to me. And being able to respond to, or echo other speakers feels valuable.
@BenedekGagyi @jsheroes @AnjanaVakil @alexnmoldovan @aleretegan @alexpausan @stephaniecodes @notbrent @markdalgleish @alinilea @NikkitaFTW @sarah_edo @xavczen @jefflembeck @lucabogdan @CompuIves @ev1stensberg #dubnation!
@jsheroes People at #jsheroes keen to see a slightly better view of how preview builds are generated by @netlify from your pull requests - here's a very short video:
https://www.youtube.com/watch?v=NVy_N5rjNdg
https://www.youtube.com/watch?v=NVy_N5rjNdg
@gautam @alexnmoldovan Yay!
And when CI/CD, Staging, Production and CDN are all in the same "box", the pain is reduced further.
And when CI/CD, Staging, Production and CDN are all in the same "box", the pain is reduced further.
Heading towards early retirement. https://twitter.com/notwaldorf/status/987323223246295040