dekobon
Joined 11 years ago
Karma
72
Submissions
35
Member since
Mar 24
Recent submissions
Comment · 3 months ago
This project allows you to create hooks in your coding agents that will get triggered when your complexity numbers exceed a threshold and will prompt for a refactor.
Comment · 1 year ago
I did a google search for the desync problem and found this page: https://my.f5.com/manage/s/article/K30341203
This type of thing is out of my realm of expertise. What information would you want to see about the problem? What would be helpful?
Comment · 3 years ago
Isn't the good part of the core team part of EnterpriseDB?
Comment · 3 years ago
It isn't documented, but if I recall correctly UNIT supports JSON with comments.
Comment · 3 years ago
Regarding #1, NGINX has created a project to make ACME integration easier. It is quite new, so I doubt it will replace your use of Caddy, but it is worth consideration.
Comment · 3 years ago
Proxy WASM appears to be supported thanks to a project from Kong: https://github.com/Kong/ngx_wasm_module
I haven't tried it yet, but it looks promising.
Comment · 3 years ago
DNS resolution may be coming: https://mailman.nginx.org/pipermail/nginx-devel/2022-July/5E...
Comment · 4 years ago
Data from these numbers is protected by HIPAA and callers can voluntarily be anonymous.
Comment · 4 years ago
Disclaimer: I am one of the authors of the project.
I do wish that NGINX made LetsEncrypt as easy as to use as Caddy does. We are all big fans of LetsEncrypt and are quite happy to see NGINX donating to the project.
In this project (MARA), LetsEncrypt support is integrated via [Cert Manager](https://cert-manager.io/) for Kubernetes. This is nice because it supports certs from a variety of issuers like AWS, Google, Vault, Cloudflare, etc in addition to Let's Encrypt.
Comment · 4 years ago
Prosper comes to mind: https://www.mayerbrown.com/en/perspectives-events/publicatio...
They didn't fall apart but got fined.
Comment · 5 years ago
Author of the article and project here...
SeaweedFS and this project have different purposes. This project is intended to show off how to configure NGINX to act as a S3 proxying gateway by using [njs](https://nginx.org/en/docs/njs/). If you look at the github for it, you will see it is just a collection of nginx config and javascript files. This all works will standard open source NGINX. All it does is proxy files like a L7 load balancer, but in this case, it adds AWS v2/v4 headers to the upstream requests.
As for caching, that is totally configurable to whatever you want; the example configuration is set to 1 hour but that is arbitrary. In fact, one of the interesting this is all of the additional functionality that can be enabled because the proxying is being done by NGINX.
Regarding read and write, that can be enabled for AWSv2 signatures, but it is more difficult to do in AWSv4 signatures. I have an idea about how to accomplish it with v4 signatures, but it will take some time to prototype it.
What is "asynchronous write back"?