Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bobfunk
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
121.
▲
by
bobfunk
11y ago
133ms latency (in the best case) is insanely bad for a database connection! Even just adding 100ms latency to Google's page load time had a clear measurably effect on # of searches, and having 100+ms latency for each database request d
122.
▲
by
bobfunk
11y ago
We're working on an open-source CMS for static site generators at netlify. It's still in beta, but we just opened up the repo here: https://github.com/netlify/netlify-cms Since netlify can already run the bui
123.
▲
by
bobfunk
11y ago
Missing Roots on that list http://roots.cx/
124.
▲
by
bobfunk
11y ago
You can shoot me a mail at matt@netlify.com
125.
▲
by
bobfunk
11y ago
One thing you can do to make this use-case work better is to combine the spreadsheet as API with a static site generator. I made this very basic plugin for Jekyll: https://github.com/netlify/jekyll-gdrive That'll
126.
▲
by
bobfunk
11y ago
Very very cool! Great news!
127.
▲
by
bobfunk
11y ago
Biilmann here, I'm definitively not at Facebook no :) I've run Haskell services in production for more than 4 years and still operate 4 of them to this date. I also contributed the wai-eventsource module to the Yesod project and b
128.
▲
by
bobfunk
11y ago
Yeah, I'm not at Facebook, but runs Netlify. I still have several services written in Haskell running in production and they've been rock solid for years now. For the kind of problems I used to solve with Haskell (typically tasks
129.
▲
A Great, Fast Static E-Commerce Experience with 6 Easy Tools
(netlify.com)
1 points
by
bobfunk
11y ago
|
0 comments
130.
▲
by
bobfunk
11y ago
Definitively the most promising project in this space in very, very, very long time! There's such a bad need for a rich text editor that doesn't just mess with HTML in a contentEditable field and tries to hack around all the issue
131.
▲
by
bobfunk
11y ago
Lets face it - responsive images can be made so complex that we end up just giving up dealing with them. This is a small plugin that aims to make it completely straight forward to at least do a good job of handling pixel densities. Won'
132.
▲
Show HN: Simple Responsive Images with Jekyll
(netlify.com)
3 points
by
bobfunk
11y ago
|
1 comments
133.
▲
by
bobfunk
11y ago
That's strange! Just tried to send myself a few test mails to that mail, and it works fine here... You can try our general mail, info@netlify.com
134.
▲
by
bobfunk
11y ago
Founder of netlify and BitBalloon here. We are working on an editing interface for static websites that can compete with the ease of use and flexibility of wordpress. Our alpha users love it and this is an open source project. We've be
135.
▲
Hugo on Netlify == speed 6 seconds from Git push to live site on global CDN
(netlify.com)
4 points
by
bobfunk
11y ago
|
1 comments
136.
▲
by
bobfunk
11y ago
Nice work! If you're interested in an option that guarantees atomic deploys and rollbacks across all files in a deploy (not just individual HTML files), handles instant cache invalidation (no 1 minute wait), and comes with built-in con
137.
▲
by
bobfunk
11y ago
API access is a lot more permissive. A deploy key only have access to 1 repo, but there's no way to limit API tokens to a single repo (and by default they have access to all repos in all organizations the issuer of a token have access
138.
▲
by
bobfunk
11y ago
Check out Netlify ( https://www.netlify.com ), we're pretty much like a paid version of Github pages. Full SSL support, integrated build automation (not just for Jekyll), redirects, built-in performance optimizations, rewrite
139.
▲
by
bobfunk
11y ago
We have an article on our blog about some of the differences. Typically you'll have to do quite a bit of work to get the same performance on S3+CloudFront as out of the box with Netlify, and if you do set up things to be as fast there,
140.
▲
Show HN: Twickr – open-source Go tool for sending tweets of interest to Slack
(netlify.com)
3 points
by
bobfunk
11y ago
|
1 comments
141.
▲
by
bobfunk
12y ago
Yup, pretty heart attack inducing the first time you get one of these!
142.
▲
by
bobfunk
12y ago
A bit too early to drop a lot of details in public, but feel free to write me (mathias@netlify.com) and I'll be happy to share more details. We want to solve the issue of having non technical content editors when working with static si
143.
▲
by
bobfunk
12y ago
We're planning on open-sourcing the Docker image that runs our build so people can send pull requests for tools we're missing. If you follow us on Twitter/FB/Newsletter etc, you'll get notified when we're ready
144.
▲
by
bobfunk
12y ago
Aside from a lot of technical details and extra features, caching details, performance tweaks etc, etc, the vision is the big difference. Our big vision is to make static sites a viable mainstream alternative to Wordpress, Drupal, Joomla, e
145.
▲
by
bobfunk
12y ago
We haven't actually started injecting it into free sites with custom domains yet, and we're still tweaking it. The goal is a balance between something that visible enough that for profit sites will want to pay for a subscription,
146.
▲
by
bobfunk
12y ago
Our CDN is global yes. Actually, when you deploy to netlify, we'll fingerprint all your assets (CSS, JS, images) and rewrite the URLs in your HTML so we can serve those straight out of Akamai's CDN with a 1 year max-age. We run ou
147.
▲
by
bobfunk
12y ago
Awesome, do let us know any feedback you have once you try it out! You can do manual deploys (both from CLI and via drag'n drop) with netlify as well, and when you're prototyping or just throwing something online quickly, that
148.
▲
by
bobfunk
12y ago
Sorry about that, should definitively improve the UI for Firefox based drag'n drop deploys. Chrome is currently the only browser that supports dragging a whole folder directly into the browser and uploading that way (so that's why
149.
▲
by
bobfunk
12y ago
Works great with Angular SPAs. Our web UI is actually an Angular SPA hosted on Netlify and using our API. You can easily setup a rewrite rule to serve your index.html instead of giving 404's so it works with history push state and we a
150.
▲
by
bobfunk
12y ago
We do the proxying straight from our CDN nodes, so it basically works like putting a CDN in front of the app/site you're proxying. This also means you have an HTTP cache in front of the proxied site, so if you use HTTP caching hea
More ›