bobfunk

18 ms·

31.
by bobfunk 7y ago
Docs are still a bit rough, but the README here should help: https://github.com/netlify/netlify-dev-plugin#project-detect...
32.
by bobfunk 8y ago
It's the only option with the current OAuth model, however, we only use the token generated in your web browser, and talk directly to GitLab's API from there. We use the token to add a deploy key and a webhook to the specific repo
33.
by bobfunk 8y ago
Yeah, we integrate pretty deeply already. We do have some new flows that could potentially make the story around publishing to Netlify from GitLab cloud seamless from an authentication standpoint, would be happy to brainstorm!
34.
by bobfunk 8y ago
Lots of people use Netlify with GitLab as well. Some using our connection to GitLab and some pushing from GitLab's CI to Netlify via CLI.
35.
by bobfunk 8y ago
We started out bootstrapping and were profitable before our first round of funding. However, we always strongly believed that the larger vision of what we wanted to build would be impossible to achieve without outside funding.
36.
by bobfunk 8y ago
We used to have those charts per site generator on the detail page before the Middleman -> React Static rewrite of the site. Would love to see them back myself. Pull Request at https://github.com/netlify/staticgen w
37.
by bobfunk 9y ago
To me the proposal there is arguably even scarier than what AMP is doing now. It requires changing browsers, to let people distribute Google Hosted Apps on their own domains (as long as Google approves). Sites distributed in this way will g
38.
by bobfunk 9y ago
Netlify CMS is a self-standing open-source project. We maintain it and are puring a lot of resources into it, because we think it's really important there's a good open-source solution on the market for projects built with static
39.
by bobfunk 9y ago
I've setup that flow by adding a custom script in the google doc that triggers a Netlify build hook. You can tie custom scripts to an image (so you can make it a publish button).
40.
by bobfunk 9y ago
At Netlify we're multi cloud - currently run our infrastructure across 7 different cloud providers and are constantly expanding.
41.
by bobfunk 9y ago
Make sure your people take vacations once in a while?
42.
by bobfunk 9y ago
Jekyll works well with Netlify - you might just have needed a Gemfile or the like?
43.
by bobfunk 9y ago
Have you checked the pricing recently? I think it's likely to have changed quite dramatically since after you switched to Firebase.
44.
by bobfunk 9y ago
The features not included in free are not typically things you can't do without for personal projects (ie, password protection, role based access control, role management for team members, etc...)
45.
by bobfunk 9y ago
Netlify as a service doesn't really affect how you do things as a front-end developer, but we do help make sure that all those assets get to your browser as fast as can be. But yes, we all agree that we should do a better job of making
46.
by bobfunk 9y ago
For small/personal sites the pricing model is "Free". I think that tends to work well :)
47.
by bobfunk 9y ago
We do support GitLab on prem already, but right now it doesn't let you trigger deploy previews and branch deploys. Currently that's something we can help with on the custom plan, but we do hope to bring it to the normal tiers as w
48.
by bobfunk 9y ago
Sure is ;)
49.
by bobfunk 9y ago
We're working on that! Main challenge is in making sure we don't inadvertently get people's domains stuck in Let's Encrypts rate limiting...
50.
by bobfunk 9y ago
Think "simplify" but with "net" :)
51.
by bobfunk 9y ago
Co-founder here - Thanks so much! We do use Elm for a couple of minor projects ourself, and it works great on our platform. We also have plenty of people using Typescript or Flow with Netlify.
52.
by bobfunk 9y ago
It's a joke, we don't actually use neither left-pad nor is-positive-integer...
53.
by bobfunk 9y ago
"do visitors mainly go to the www or no-www version of your site?" Visitors follow links - just checked netlify.com vs www.netlify.com and over the last 3 days around 0.5% of visits went to netlify.com instead of straight to www.n
54.
by bobfunk 10y ago
It serves the HTML or assets directly
55.
by bobfunk 10y ago
If you read the start of the article you'll see we do that as well. This only applies to people that don't use netlify for DNS.
56.
by bobfunk 10y ago
With HTTP2 support this is not longer really a problem, since HTTP2 multiplexes requests over 1 connection.
57.
by bobfunk 10y ago
We do run an anycast CDN network, but there's a lot of limitations on BGP routing compared to CDN based traffic direction. We can only route BGP requests to hardware we control, whereas we can add PoPs in all the major cloud providers
58.
by bobfunk 10y ago
That would be great to see and would solve a real issue for many users of services like ours (or Heroku, GitHub pages, etc, etc, etc). There are gotchas however, since you now depend on two levels of DNS based traffic direction and we have
59.
by bobfunk 10y ago
Author here. We do actually offer all of these options. We offer a public IP address for A records pointing to a our main load balancer. This will send all traffic to a single origin instead of serving your HTML pages out of our global CDN.
60.
by bobfunk 10y ago
It's also worth noting that Smashing Magazine is not just articles (and comments), but also a full E-commerce, job board, event page, ticket checkout and introduced a new membership section with subscriptions. Obviously all of that can

More ›