@salehczk @patio11 @Netlify @letsencrypt While @netlify may be a good match for the podcast site, you may want to consider where the podcast audio files are served from. There is a 10MB maximum file size on the CDN.
https://www.netlify.com/docs/build-gotchas/
@_leilaura @Netlify @smashingconf It's worth making sure that the version of ruby used by @Netlify during your builds, is the same as in your local builds. You can define that with a .ruby_version file.
https://www.netlify.com/docs/continuous-deployment/
https://www.netlify.com/docs/continuous-deployment/
@budparr @bepsays @ChrisShort @GoHugoIO @Medium @IFTTT @Netlify I also use @IFTTT to pull tweets into my #jamstack site. But to schedule builds you could use @zapier and webhooks with @Netlify
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
Reflecting on @smashingconf London. What a wonderful event to be a part of. Exceptional talks. Friendly & enthusiastic people. Expert MC-ing from @una and @patrickhamann.
And the talks are already online!
Mine: https://vimeo.com/254678463
#workflow
#casestudies
#jamstack
#git
#CI
And the talks are already online!
Mine: https://vimeo.com/254678463
#workflow
#casestudies
#jamstack
#git
#CI
@psd @Jack_Franklin Oh my! I missed this announcement! What a fabulous innings at GDS. I'd be very excited to hear all about what's next over a cold fizzy drink.
Just name the day and I'll finish this champagne and jump in the helicopter to meet both you lovely fellas for a drink to celebrate.
Just name the day and I'll finish this champagne and jump in the helicopter to meet both you lovely fellas for a drink to celebrate.
This is fascinating to watch! https://twitter.com/anatudor/status/961580469044301833
If you need me I'll be watching this over and over and over and over and over and over again.
https://twitter.com/semibogan/status/961172614843547653
https://twitter.com/semibogan/status/961172614843547653
@MarkyMarkNo1 Glad that was useful!
I don't have a set of pre-baked tools for these things to hand, but hope examples like this show how simple it is to stitch mainstream services together with some fundamental techniques.
Hoping it doesn't feel exotic.
Trigger / fetch / store / build
I don't have a set of pre-baked tools for these things to hand, but hope examples like this show how simple it is to stitch mainstream services together with some fundamental techniques.
Hoping it doesn't feel exotic.
Trigger / fetch / store / build
@MarkyMarkNo1 I've not used it to be hinest. But it reads well and looks good. I'm pretty open to different sets of tools and think it's good to have the freedom to choose whatever suits your style and requirements best.
@brucel @smashingconf Bruce doesn't know better but I'm disappointed in the rest of you. Making a note of all of the people who *like* this tweet. Consider your cards marked.
OMG! Thanks is now by favourite tweet of all time.
I will now ONLY do workshops where @rafahari is available to perform this move! https://twitter.com/rafahari/status/961640252036276226
I will now ONLY do workshops where @rafahari is available to perform this move! https://twitter.com/rafahari/status/961640252036276226
@JoCoOne @smashingconf No cigar for you, I'm afraid.
Emojis are not the official theme... they're just awesome.
😎🚇😎
Emojis are not the official theme... they're just awesome.
😎🚇😎
@simonmcmanus @Netlify @greenkeeperio You can fire webhooks based on different events such as a successful/failed build. And you can trigger builds on different branches via an incoming web hooks.
So it is more like you have the Lego pieces to make this, rather than having the specific feature you mentioned.
So it is more like you have the Lego pieces to make this, rather than having the specific feature you mentioned.