@johneas10 @Netlify I'm afraid that this is not possible.
We can transfer domains out. But not in. (since we are not a direct registrar)
@paulrobertlloyd @bastianallgeier @Netlify That is not our goal, plan, strategy or roadmap.
I understand the observation and caution, and we've exchanged thoughts on this before. But how does one ever use any service if the concern is that the good places will *always* get purchased by the bad?
I understand the observation and caution, and we've exchanged thoughts on this before. But how does one ever use any service if the concern is that the good places will *always* get purchased by the bad?
@brendandawes @bastianallgeier @Netlify The free tier is a valuable way to experience and gain confidence in the platform. But if your site is business critical, perhaps then consider one of the paid tiers which can provide SLAs and are where Netlify make $.
Also, #jamstack sites are super portable (but don't go! 😭)
Also, #jamstack sites are super portable (but don't go! 😭)
Last night's @ItsHumdingers was so much fun. Feeling pretty fortunate to host such a friendly night of comedy and introduce the superb:
@MrRyanJDalton
@tomwardvoice
@Izzymant
and
@Jarlath
@MrRyanJDalton
@tomwardvoice
@Izzymant
and
@Jarlath
@sallylait @elibelly oh.
👋
I'll check my email, @sallylait!
And these few short videos might help trigger some thoughts, @elibelly:
Spit tests:
https://www.youtube.com/watch?v=5VgpJJUOng4&list=PLFpA-5bXKuTrGfqel_6JCx1EBIAhgNC3F
Tracking tests with GA
https://www.youtube.com/watch?v=ujqM2lMRDkg&list=PLFpA-5bXKuTrGfqel_6JCx1EBIAhgNC3F&index=5
Split test for opt-in betas:
https://www.youtube.com/watch?v=Q5-QTaAOSrY&list=PLFpA-5bXKuTrGfqel_6JCx1EBIAhgNC3F&index=2
👋
I'll check my email, @sallylait!
And these few short videos might help trigger some thoughts, @elibelly:
Spit tests:
https://www.youtube.com/watch?v=5VgpJJUOng4&list=PLFpA-5bXKuTrGfqel_6JCx1EBIAhgNC3F
Tracking tests with GA
https://www.youtube.com/watch?v=ujqM2lMRDkg&list=PLFpA-5bXKuTrGfqel_6JCx1EBIAhgNC3F&index=5
Split test for opt-in betas:
https://www.youtube.com/watch?v=Q5-QTaAOSrY&list=PLFpA-5bXKuTrGfqel_6JCx1EBIAhgNC3F&index=2
@leemartin @Netlify The @Netlify API awaits...
https://www.netlify.com/docs/api/
This display awaits....
https://www.theverge.com/circuitbreaker/2018/1/11/16876582/vestaboard-mechanical-split-flap-display-internet-train-sign-ces-2018
The world awaits...
(I dare you!)
https://www.netlify.com/docs/api/
This display awaits....
https://www.theverge.com/circuitbreaker/2018/1/11/16876582/vestaboard-mechanical-split-flap-display-internet-train-sign-ces-2018
The world awaits...
(I dare you!)
@marcelfahle @erikras @Netlify Ha ha. Yeah, and transforming a podcast with nf_resize=smartcrop will trim out all the ads. 😝
@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/
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.