@erikras @Netlify Using Netlify Large Media for the management of the assets in your repo won't change your bandwidth usage or limits when serving the files up.
Those limits and costs are summarised here: https://www.netlify.com/blog/2019/02/26/netlify-and-bandwidth/
@jaffathecake @SaraSoueidan @duncanmacgregor @Netlify @deployhq I like to invoke the Seinfeld slap bass.
@SaraSoueidan @duncanmacgregor @Netlify @deployhq ...@Netlify would not serve a site using MySQL. Instead, sites which depend on content in a CMS, use a decoupled model and pull the content in from a headless CMS at site build time.
If data is required at request time, we'd typically use #serverless functions and a DBAAS.
If data is required at request time, we'd typically use #serverless functions and a DBAAS.
@SaraSoueidan @duncanmacgregor @Netlify @deployhq š
That's right @duncanmacgregor, @Netlify will pull your code, run your build in a CI/CD environment, and then deploy the output to our global CDN. The model is to pre-build the site so it runs entirely from the CDN with no origin server to maintain.
See https://www.netlify.com/features/
That's right @duncanmacgregor, @Netlify will pull your code, run your build in a CI/CD environment, and then deploy the output to our global CDN. The model is to pre-build the site so it runs entirely from the CDN with no origin server to maintain.
See https://www.netlify.com/features/
*Another* pain point addressed!
I can't wait to start using this capability. https://twitter.com/Netlify/status/1100465821544075264
I can't wait to start using this capability. https://twitter.com/Netlify/status/1100465821544075264
@plambweb @kentcdodds @Netlify Ha! I hear that!
I ended up with a domain that was not particularly short, but felt meaning full to say/hear (which suited my needs, when using it in presentations)
https://findthat.at/the-place-I-said
I ended up with a domain that was not particularly short, but felt meaning full to say/hear (which suited my needs, when using it in presentations)
https://findthat.at/the-place-I-said
@pomber @Netlify @Namecheap Ha ha!
(I gather that you should already have received a response. Could you double check that it hasn't slipped past?)
(I gather that you should already have received a response. Could you double check that it hasn't slipped past?)
@pomber @Netlify @Namecheap If you are having DNS config woes, I'd recommend contacting the support team via https://netlify.com/support. they may be able to help you out.
@sebastienlorber @superpatell @Netlify Ha. Sorry. Several threads. Few characters š
A good start is reducing the attack surface by pre-building sites and removing the webservers from the scenario at request time. Beyond that, serving from a CDN which can withstand the failure of several global cloud platforms is..šŖ
A good start is reducing the attack surface by pre-building sites and removing the webservers from the scenario at request time. Beyond that, serving from a CDN which can withstand the failure of several global cloud platforms is..šŖ
@superpatell @sebastienlorber @Netlify In the 1st instance, you'd need to manage all assets deployed into an external CDN from Netlify's CDN, treating it like an origin. Netlify does all of that for you already with millisecond speeds for cache invalidation on global atomic deploys.
The 2nd depends on the other CDN.
The 2nd depends on the other CDN.
@sebastienlorber @Netlify Netlify's ADN is globally distributed like other CDNs, and has similar DDOS mitigation. Except it also spans 7 different cloud providers for reasons of resiliency and performance.
https://www.netlify.com/features/adn/
https://www.netlify.com/features/adn/
@sebastienlorber A sensible question.
@Netlify exists precisely to address this kind of concern. A combination of pre-generating sites at build time, removing the notion of an origin server, and delivering everything directly from a multi-cloud, distributed ADN, bring high capacity/availability.
@Netlify exists precisely to address this kind of concern. A combination of pre-generating sites at build time, removing the notion of an origin server, and delivering everything directly from a multi-cloud, distributed ADN, bring high capacity/availability.
@superpatell @sebastienlorber @Netlify @zeithq @cloudfront @Cloudflare I'd suggest not doing that.
One of the advantages of this pre-rendered or #JAMstack approach on @Netlify is that your site is served directly from our distributed CDN. It's designed for this scenario. By adding a CDN in front of the CDN, you'll add latency and complexity.
One of the advantages of this pre-rendered or #JAMstack approach on @Netlify is that your site is served directly from our distributed CDN. It's designed for this scenario. By adding a CDN in front of the CDN, you'll add latency and complexity.
I don't know who @slightlylate thinks he is, swooping in with a useful solution which disrupts my ability to grumble into the void like a spoilt brat.
https://twitter.com/philhawksworth/status/1100080104057856001
https://twitter.com/philhawksworth/status/1100080104057856001
@igorakkerman @Netlify I see.
I think that there is more to providing this than just a field in a db. As with many things, managing all possible user flows, and the unhappy path along with the happy path in the UI, can make things complex to build.
But this is useful feedback. Thanks
I think that there is more to providing this than just a field in a db. As with many things, managing all possible user flows, and the unhappy path along with the happy path in the UI, can make things complex to build.
But this is useful feedback. Thanks
@mrhesselbom @Deanacus @Netlify Glad that these are all working ok. DNS is one of those tricky things where actions set in motion on various places around the world can have an effect... in their own sweet time!
Pleased all is well. Support will certainly be happy to help if you run into other issues there.
Pleased all is well. Support will certainly be happy to help if you run into other issues there.
@mrhesselbom @Deanacus @Netlify Iād suggest emailing support@netlify.com. The team there should be able to help out.
Wow. Seeing your own name on this list is quite special.
This event is going to be rather brilliant. https://twitter.com/heypresents/status/1100070786210119680
This event is going to be rather brilliant. https://twitter.com/heypresents/status/1100070786210119680
@igorakkerman @Netlify Although, you can sign in to Netlify using various services which do offer 2FA.
(Signing in with GitHub is a common example)
(Signing in with GitHub is a common example)