@jgarber @Netlify I'm asking smarter people than me... but I'm assuming that the allocation of that subdomain takes place in the post-processing, so by it's very nature, it is not available during the build.
But I'm curious about the thoughts people have. Let me come back to you.
@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.
@kosamari @Netlify aaaah! I should have read it more closely too!
And thanks! I'll pass that on to the team. @VeryThorough leads the documentation effort and she'll be pleased to hear that they are still standing up the platform grows. That work is never done!
And thanks! I'll pass that on to the team. @VeryThorough leads the documentation effort and she'll be pleased to hear that they are still standing up the platform grows. That work is never done!
@kosamari FWIW, and since you've been dabbling with it already, you can have control over your headers on @Netlify by adding a _headers file to your repo. You have full control over your CSP headers.
https://www.netlify.com/docs/headers-and-basic-auth/#custom-headers
https://www.netlify.com/docs/headers-and-basic-auth/#custom-headers
@_munter_ @Netlify This should be what you need.
https://www.netlify.com/docs/dns/#adding-dns-records
https://www.netlify.com/docs/dns/#adding-dns-records
From the URL (best pronounced in a NZ accent) to the functionality, there is nothing about this site that I don't love! https://twitter.com/kosamari/status/1011311171511705607
If I'm learning anything from the World Cup this year, it's that footballers are still far more delicate than you might imagine.
This tumblr could get a bunch more content:
https://horrific-soccer-injuries.tumblr.com/
This tumblr could get a bunch more content:
https://horrific-soccer-injuries.tumblr.com/
@AskAtlassian Any updates on the timeline or intent here? The last "please hold" message was back at the start of March.
I was ready to put the word "influencers" in the bin, but now I also want to send all of civilization along with it. https://twitter.com/JustinCaffier/status/1011334607797547008
@nullvoxpopuli @Netlify @Cloudflare The CDN is custom built to span 7 cloud providers for resilience, and is designed to be excellent for small source files. It also houses some of the clever logic which powers features at the edge like A/B testing and redirect APIs. DNS by @NS1 (🔥)
No need to add anything else.
No need to add anything else.