GitHub Pages Reviews

node-http-proxy Reviews

GitHub Pages mentions (504)

• Github as Infrastructure

  The site itself is a statically generated Next.js app, built in CI and deployed to GitHub Pages via actions/deploy-pages. No server to manage, no hosting bill. - Source: dev.to / 3 months ago

• Three Tiers of Data Freshness in a SvelteKit Static Site

  Static sites are fast and cheap to host, but your data goes stale the moment you deploy. This post shows how a SvelteKit portfolio site serves live data from five external sources while still deploying as static HTML to GitHub Pages. - Source: dev.to / 4 months ago

• Announcing Three New Free JAMstack Blogging Themes: IndiePaper, Newsprint, and brennan.jp.net

  All three themes are designed for accessible deployment. You can host them for free on Netlify, GitHub Pages, Vercel, or Cloudflare Pages. The only cost is a domain name (which can be as cheap as $5/year on Porkbun). - Source: dev.to / 5 months ago

• Testable Dotfiles Management: Building Development Environment with Chezmoi

  This action can store collected benchmark results in GitHub pages branch and provide a chart view. Benchmark results are visualized on the GitHub pages of your project. - Source: dev.to / 10 months ago

• How to Build a Python MCP Server to Consult a Knowledge Base

  But that's not the case. The blog is a simple static generated website using Jekyll, it is built and served through GitHub Pages. With that in mind it makes more sense to use tools and leverage tool calling. - Source: dev.to / 11 months ago

node-http-proxy mentions (10)

• Is there a way to accept incoming http but outgoing must be https?

  Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper. Source: over 3 years ago

• HTTPS proxy setup with response modification

  I have been tasked with writing a proxy server that takes a clients requests and forwards it to a target server (normal proxy stuff). The client and the target are out of my control. The only change in the client is that the its requests to the proxy server instead of the target. Now, what I need to do is modify the response from target because the client expects it in a certain format and the server responds... Source: almost 4 years ago

• what's the stack for this application?

  What you're describing is a proxy server. If you wanted to use Node.js check out https://github.com/http-party/node-http-proxy. Notice that the examples there just forward the req though which potentially has identifying information like cookies, so you'll need to rework to anonymize. Should be straightforward. Source: about 4 years ago

• GraphQL is now available on Supabase

  There's several ways to have a blog path contain a separate setup from the marketing/product routes. One is to run a reverse proxy on the root domain to pull in separate routes for various services. https://github.com/http-party/node-http-proxy You can do rewrites at the server level for the root domain Or if the app on the root domain can do the routing for you (have done this before with a Rails app). - Source: Hacker News / over 4 years ago

• Creating and deploying a tiny proxy server on Vercel in 10 minutes

  Check the documentation of the http-proxy-middleware library (and of the node-http-proxy library, used under-the-hood) to learn how you can manipulate the proxied request & response. - Source: dev.to / over 4 years ago