@DavidDarnes Ah.
...which I now notice you have already done!
@DavidDarnes Great! You can also use a custom domain or just rename it to user a meaningful site nam and grab a subdomain for it.
@elefontpress And who would have thought that possible?!
I still don't understand how he keeps appearing in our papers and on our TV. The toxic little toad really needs to quietly go away.
I still don't understand how he keeps appearing in our papers and on our TV. The toxic little toad really needs to quietly go away.
I hope that after eating some raspberry jam, he gets a single seed stuck in one of his molars so his bite feels funny. And he can neither get it out nor stop poking at it with his tongue. So he ends up with a sore, achey tongue. https://twitter.com/mrdavidwhitley/status/941999102241501185
@DavidDarnes The drag and drop only deploys the assets you drop there... for a build to run, you need to link to a repo.
Or you can run your build locally and push the output to Netlify via the API.
https://www.netlify.com/docs/cli/
Or you can run your build locally and push the output to Netlify via the API.
https://www.netlify.com/docs/cli/
@anna_debenham @snyksec How dare you!?
I do not have an enormous head.
(Yes it does. Thanks for sending one with a stretchy "maternity panel")
I do not have an enormous head.
(Yes it does. Thanks for sending one with a stretchy "maternity panel")
@DavidDarnes @eduardoboucas @staticmanapp @heroku @Netlify @NetlifyCMS If you can run a build, you should be able to run that build on Netlify. Keen to hear how you get on.
@eduardoboucas @DavidDarnes @staticmanapp @heroku @Netlify Nice! @NetlifyCMS does some similar things by giving a UI for users to admin content into a git workflow (without needing to know git!), and Netlify itself has form handling and auto build triggering built in.
That said, the more tools and hosts for #jamstack sites the better!
That said, the more tools and hosts for #jamstack sites the better!
@robmuh @tjholowaychuk @Netlify @surge_sh Yep. Netlify will try to delegate as much as possible out to CDN edge nodes to significantly reduce latency for visitors wherever they are. That includes the logic for language and location-based redirects, and even the split (A/B) testing which can all happen at the edge.
@tjholowaychuk @robmuh @Netlify @surge_sh Yep. Although Netlify's _redirects run directly on the edge CDN nodes so can be super fast. Can even be faster than DNS in some cases (since you save the DNS lookup and CORS preflight requests, etc)
And then Paul played his trumpet in a concert.
And he was a good boy.
And he looked smart.
So he got an ice cream.
And he was happy. http://ift.tt/2k3A9Ih
And he was a good boy.
And he looked smart.
So he got an ice cream.
And he was happy. http://ift.tt/2k3A9Ih
@robmuh @tjholowaychuk @Netlify @surge_sh Curious to hear what a new dev might need beyond the free tier on Netlify. The ceiling is waaay high. For a #jamstack site with added Lambda power, I tend to define proxy rules to route URLs to my Lambdas (it feels like cheating!).
See proxying — https://www.netlify.com/docs/redirects/
See proxying — https://www.netlify.com/docs/redirects/
A very early bird! But such a juicy worm.
Highly recommended. https://twitter.com/coldfrontconf/status/941624399312060417
Highly recommended. https://twitter.com/coldfrontconf/status/941624399312060417
@SamuelDev @Netlify Awesome! Glad you're having such a good experience.
I spoke to the team and we all agree that the best way for you to compensate us is for you to buy me a beer next time I'm in Canada.
(that might not be 100% true)
I spoke to the team and we all agree that the best way for you to compensate us is for you to buy me a beer next time I'm in Canada.
(that might not be 100% true)