61–70 of 79 posts
I’m amused this is here. This was a random reply to someone who thought maybe we were doing this. To be clear: that’s all this is. But I’m happy to hear all the suggestions.
Do you have some kind of a script for these CF threads or do you just spend that much time on HN? :)
Cloudflare folks. Please don’t do this. I don’t know if Mr.Cumming is serious. As a user of CF, I hope you folks go a lot deeper than broader. Example: Better cache management – compete with Fastly, my tickets on load balancer bugs were open for almost 6 months, etc.
Another example: unify all the separate "rule" types. There's page rules, firewall rules, IP access rules, user agent rules, etc. It can get unwieldy.
Earlier quoted context omitted.
We care a lot about the product and the people who use it.
If only you could say the same about potential employees. Your recruiters seem to have a penchant for completely ghosting candidates, even when several interviews deep into the interview process. This has happened to me twice now, with two different recruiters, even after being told by the interviewers that I was well qualified and surely would be moving to the next step. And after glancing at Glassdoor reviews, this…
Earlier quoted context omitted.
If we smash them together we'd get Gitgit, which is probably the best option.
I need a name for our internal Gitea instance, do you mind if I grab this idea? Haha. * gitgit.at — as in, gitgit.at/username/ * gitgit.dev * gitgit.ist — sounds funny
More seriously. I’d be curious to hear about what you’d build on our network. We are all over the world and it would be fun to hear about companies other than GitHub that you think we should disrupt.
I’d like to be able to have more than one unique Cloudflare worker per account. And be able to assign specific workers to specific routes. This feels like an odd limitation and forces you to make huge workers code with path case statements to separate the request actions out. Pretty soon a single worker starts to feel like a large app instead of a simple function that does mostly one thing.
The ability to have more than one worker or at least a “dev” worker is really showing to be important to me. Especially the more logic that is moved to the edge, the more complex it gets, and the more testing/review might be needed so you need some way to stage changes before promoting to production.
Overall though I really like Cloudflare workers. I’ve moved a project that was built on AWS and it’s mostly all an improvement on CF, especially performance which was very noticeable. I run one public API entirely on workers and I use workers on the public facing site to scrub the path users send us and 302 them to the right place, instead of having to do that in the app. I also remove most query params inside the worker to improve caching performance. I should have a use case for the KV system soon.
More seriously. I’d be curious to hear about what you’d build on our network. We are all over the world and it would be fun to hear about companies other than GitHub that you think we should disrupt.
I'm a big supporter of Cloudflare and have been using it for almost 8 years. I personally don't think doing something like that is what Cloudflare needs. What Cloudflare needs is further customization, especially in regards to caching. We actually had to migrate a certain part of our infrastructure to Fastly due to the lack of caching customization/rules. I'd like to see: - Custom caching rules similar to the new fir…
If that doesn’t help you build what you’re looking for, happy to chat via email and hear more about what you need: kristian@cloudflare
Earlier quoted context omitted.
Bare git only stores code, not issues, tickets, wiki, and all the stuff that goes beyond source files. There are a myriad of open source solutions for this, but there is no standard format that allows easy migration and inter-linking.
Well for wiki, usually a branch containing markdown will transfer well across forges. Issues and PRs are the real issue. I’ve been hoping git appraise would get supported by the forges for distributed PRs, but it doesn’t look like that’ll happen. Gitlab is implementing MRs via git send-email though, which is part of an epic to federate Merge Requests: https://gitlab.com/groups/gitlab-org/-/epics/260 .
If Cloudflare wants to branch out, here're an idea. Global Memcached or Redis. Support caches near the edges. SPA or apps running on a client's browser/machine can use the one nearby. Support pre-populating/warm-up the caches in batch.
How about Github without a big corporation? Not controlled by Cloudflare, ddecentralized and uncensorable. Like bittorrent, but for git repos, issues, etc.
So... git? It's already designed to be decentralized. Hosting a public read-only repo would be as easy as standing up NGINX and pointing it at your repo folder, afaik. At my previous job, we all had individual dev machines that we each had accounts on. So, we each had a copy of our repos that we could push to/work from. I wrote a little git alias that would add remotes for each others' machines so we could pull direc…
Earlier quoted context omitted.
So... git? It's already designed to be decentralized. Hosting a public read-only repo would be as easy as standing up NGINX and pointing it at your repo folder, afaik. At my previous job, we all had individual dev machines that we each had accounts on. So, we each had a copy of our repos that we could push to/work from. I wrote a little git alias that would add remotes for each others' machines so we could pull direc…
Bare git only stores code, not issues, tickets, wiki, and all the stuff that goes beyond source files. There are a myriad of open source solutions for this, but there is no standard format that allows easy migration and inter-linking.