calavera

8 ms·

1.
Benchmarking the Most Reliable Document Parsing API(tensorlake.ai)
28 points by calavera 11mo ago|14 comments
2.
eBPF and Rust(kbknapp.dev)
2 points by calavera 6y ago|0 comments
3.
Run WebAssembly Everywhere(medium.com)
2 points by calavera 7y ago|0 comments
4.
How Netlify’s deploying and routing infrastructure works(medium.com)
2 points by calavera 9y ago|0 comments
5.
NetlifyCMS 1.0, Git-based content management to static sites(netlify.com)
6 points by calavera 9y ago|2 comments
6.
by calavera 9y ago
Hi, CTO of Netlify here, let us know if you need any help moving out docs, websites or any other web property from there, we'll be super happy to help. Projects like Kubernetes, Docker and React are already using our free offering for
7.
Netlify introduces TOML Structured configuration(netlify.com)
2 points by calavera 9y ago|0 comments
8.
by calavera 9y ago
this webpack plugin might help you: https://gist.github.com/Kamshak/35630ec21df8dca27de3bb915f2d... I have no idea why the original comment by the author is shadow banned.
9.
by calavera 9y ago
I just deployed a change that we think it should fix the problem in your site, we're going to keep an eye on it \o/
10.
by calavera 9y ago
Hey StavrosK, don't hesitate to reach out to Netlify support. I'd love to take a look at your site to figure out what's going on there.
11.
HTTP/2 Server Push on Netlify(netlify.com)
64 points by calavera 9y ago|23 comments
12.
Netlify Plus Hugo 0.20 and Beyond(netlify.com)
4 points by calavera 9y ago|0 comments
13.
by calavera 10y ago
Hi, Netlify CTO here. You're right, everything that the CMS does currently could also be done with raw Git messages. The CMS is designed to have pluggable backends. We had an early version working with Git directly. We decided to focus
14.
Keep your site stable with Locked Deploys – Netlify(netlify.com)
3 points by calavera 10y ago|0 comments
15.
Pubstorm is shutting down(pubstorm.com)
2 points by calavera 10y ago|0 comments
16.
by calavera 10y ago
I agree with you, $10 in AWS fees sounds like a lot of traffic. That's also why Netlify has a free tier. We leave paid plans for people with more traffic. We event have a redundant DNS service for people that really really need it. For
17.
by calavera 10y ago
that tutorial is pretty awesome, very well written. Netlify can do everything you explain there by running one single command line. Check this video out: https://www.youtube.com/watch?v=IfFenanuRnc&feature=youtu.be
18.
by calavera 10y ago
Netlify Pages is our free tier that offers a few things that GitLab Pages doesn't offer. For instance, we build merge requests for you and integrate them with commit statuses. So you get a real development workflow for your websites. C
19.
by calavera 10y ago
CloudFront is good. We use it for large assets. After managing thousands of sites, we realized that it's actually a hassle to manage cache invalidation yourself. We work with several cloud providers to offer a better experience at the
20.
by calavera 10y ago
Hi, Netlify CTO here. It's great that a combination of those services works for you. Our initial tier is completely free, $0. No costs per traffic nor storage, unlike S3. Please, feel free to send questions and I'll be happy to an
21.
by calavera 10y ago
Thanks! Signup permissions is definitely something we need to work on more. We optimized them at the beginning to give people the best experience possible, but we'll definitely iterate to allow using Netlify with less permissions. We j
22.
by calavera 10y ago
Netlify CTO here (so I'm very biased). These are some things that you can do with our Pages tier FREE , that you cannot do with GH Pages: - We don't restrict people to only one static site generator, like Jekyll. You have use wha
23.
by calavera 10y ago
Thanks Sid! It was actually very easy to integrate. Thanks for making the API so easy to use.
24.
by calavera 10y ago
being able to see pull requests deployed live without compromising production changed drastically the way we work as a team and we build our front-end applications. I can't wait to get other people's feedback.
25.
Refactoring towards presentational components in React(purple.netlify.com)
1 points by calavera 10y ago|0 comments
26.
Simplicity and the ideas Go left behind(sourcegraph.com)
79 points by calavera 12y ago|88 comments
27.
by calavera 13y ago
we use d3 for all our charts.
28.
by calavera 14y ago
Yes, the testing/deployment cycle for Enterprise is totally different. We usually release a major version with new features every two/three months, and 2 or 3 minor versions with bug fixes in between. We always keep the version of github sy
29.
JRuby class loader by example(thinkincode.net)
2 points by calavera 16y ago|0 comments