einshutoin

9 ms·

1. 1.▲
   Show HN: A single security policy for both AWS CloudFront and Cloudflare Workers

   1 points by einshutoin 7mo ago|0 comments
2. 2.▲
   by einshutoin 7mo ago

   I built a small OSS that lets you define CDN security rules in YAML and compiles them into edge JavaScript. Motivation: - avoid config drift - make security rules reviewable - GitOps-friendly workflow Looking for feedback from SRE / Pl
3. 3.▲
   Show HN: YAML-based security framework for CDN edge (CloudFront / Cloudflare)(github.com)

   1 points by einshutoin 7mo ago|1 comments
4. 4.▲
   by einshutoin 7mo ago

   Hello HN, I built cdn-security-framework because I was tired of the "manual sync" problem between my security policies and my edge code. Usually, you define security headers in one place, rate limits in another (WAF), and custom b
5. 5.▲
   Show HN: A Compiler for CDN Security (YAML to CloudFront/Workers/WAF)(npmjs.com)

   1 points by einshutoin 7mo ago|1 comments
6. 6.▲
   by einshutoin 9mo ago

   Hi HN, I recently shared `lazy-image`, a Rust-powered Node.js image library meant to be a drop-in replacement for Sharp in serverless environments. Some of you asked for reproducible benchmarks. So I built a Dockerized test environment with
7. 7.▲
   Show HN: Dockerized benchmark suite for Sharp vs. Lazy-Image (Rust-based)(github.com)

   2 points by einshutoin 9mo ago|1 comments
8. 8.▲
   by einshutoin 9mo ago

   Currently, lazy-image does not support Cloudflare Workers. lazy-image uses native modules (.node files) built with NAPI-RS, which cannot run in Cloudflare Workers' V8 Isolate environment (only WebAssembly or pure JavaScript are support
9. 9.▲
   Show HN: Lazy-image – Node.js image library with static binaries (Rust/NAPI)(github.com)

   7 points by einshutoin 9mo ago|2 comments