@paraggawde_21 @andrewakagawa @github @Netlify You can run builds on @Netlify just like you would locally, so if you use @nuxt_js, you can use build with @vuejs and then serve things directly from Netlify. You'll get all the CI and deployment workflow without needing to maintain any server.
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21
@ncphi @owenandrews_ @webdev42 @GoHugoIO @Netlify @forestryio @chrisdmacrae Yes! This is a great post. I'm always keen to see more and more experiences and advice of people using these tools together.
Uh-oh. Sending @SlackHQ some positive vibes as they work through an issue.
https://status.slack.com/2018-06/142edcb9e52c7663
As a remote worker, this means that I should just focus extra hard on a tricky task (or more likely, go for a walk in the sunshine, right?)
https://status.slack.com/2018-06/142edcb9e52c7663
As a remote worker, this means that I should just focus extra hard on a tricky task (or more likely, go for a walk in the sunshine, right?)
@greg_a @keirwhitaker @peakdesignltd They are!
Funnily enough it turns out that they are @peakdesignltd are based in the same build as us in Dogpatch! (I could have save them a delivery to me here in the UK!)
Funnily enough it turns out that they are @peakdesignltd are based in the same build as us in Dogpatch! (I could have save them a delivery to me here in the UK!)
Uh-oh. I fear that https://leaderofthepack.blog/about/ from @keirwhitaker will further fuel what seems to becoming something of a fetish for me. Backpacks and carryons.
(Currently using and loving one of these @peakdesignltd beauties, Keir. Highly recommended - https://www.peakdesign.com/product/bags/everyday-backpack)
(Currently using and loving one of these @peakdesignltd beauties, Keir. Highly recommended - https://www.peakdesign.com/product/bags/everyday-backpack)
@owenandrews_ @webdev42 @GoHugoIO @Netlify @forestryio Not to worry! Bravo for a live demonstration. Impressive!
I'd eagerly read a blog post on how you used these tools together.
😎
I'd eagerly read a blog post on how you used these tools together.
😎
@owenandrews_ @webdev42 @GoHugoIO @Netlify @forestryio Nice!
I'd love to see this. Are there any slides that I could gawk at?
I'd love to see this. Are there any slides that I could gawk at?
@marinelbrgn @Netlify Can I suggest that you email support@netlify.com? The team there are in a much better position to help.
@vlh @smashingconf Ok. Would you mind asking everyone to hang on and wait for me?
And you don't think @danmall, @LeaVerou, @sarah_edo and @tkadlec would mind just repeating their talks for me when I get there, do you?
And you don't think @danmall, @LeaVerou, @sarah_edo and @tkadlec would mind just repeating their talks for me when I get there, do you?
@bahmutov @HenrikJoreteg This has got my cogs turning.
I bet a setup that involved 2 sites on Netlify and some crafty webhooks and build triggers could create all of this without sacrificing the CI workflow that is so valuable.
I feel some experimenting coming along.
I bet a setup that involved 2 sites on Netlify and some crafty webhooks and build triggers could create all of this without sacrificing the CI workflow that is so valuable.
I feel some experimenting coming along.
@bahmutov @HenrikJoreteg Problem there is that you don't want to deploy to the CDN if your site is identified as having build errors.
Maybe ok as a configuration on branch builds (Netlify builds have contexts so that you can run different builds on all/nominated branches vs master)
Maybe ok as a configuration on branch builds (Netlify builds have contexts so that you can run different builds on all/nominated branches vs master)
@bahmutov @HenrikJoreteg All of the dependencies listed in your package.json should be cached between builds automatically. We do that quietly so that you don't need to think about deps caching. We re-run yarn / npm install if the hash of your package.json changes.
@HenrikJoreteg @bahmutov Sadly this is not possible yet. However we've been discussing adding an additional event during the build/deploy process which would enable exactly this kind of ability.
An event that fires between completing the build and propagating to our CDN where you could perform actions.
An event that fires between completing the build and propagating to our CDN where you could perform actions.