titocloud-microservice-proxy

Configures reverse proxy routing for new microservices behind TitoCloud.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill titocloud-microservice-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: titocloud-microservice-proxy
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/devops/titocloud-microservice-proxy
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill titocloud-microservice-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill shows how to add new microservices behind TitoCloud’s reverse proxy without breaking navigation, APIs, or static asset loading.

Core Features & Use Cases

  • Reverse Proxy Routing: Map a service to TitoCloud so users access it through a single entry point on port 8090.
  • Frontend Compatibility: Keep browser requests working by using relative URLs and trailing-slash-safe paths.
  • API and Body Forwarding: Pass GET, POST, and other service traffic through to the correct backend process while preserving request bodies.
  • Use Case: You are launching a new internal web app and want it available through TitoCloud with a landing page, API endpoints, and assets all routed correctly.

Quick Start

Use this skill to describe your new service name, backend port, and any proxy rules you need so it can be added safely behind TitoCloud.

Frequently Asked Questions about titocloud-microservice-proxy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a reverse proxy for microservices behind a single entry point?

To configure a reverse proxy for microservices, map your backend service to the proxy entry point on port 8090, applying prefix stripping and relative frontend URLs to keep navigation and asset loading intact.

Why does my reverse proxy break static assets and frontend navigation?

Reverse proxy routing breaks static assets when paths are not stripped correctly. You must use relative frontend URLs and trailing-slash-safe paths to ensure browser requests resolve properly through the proxy.

How do I forward POST requests and bodies through a reverse proxy to a backend process?

To forward POST requests through a reverse proxy, you must preserve the request body, handle CORS preflight, clean hop-by-hop headers, and propagate the correct content-length to the separate backend process.

Can I route API endpoints and landing pages through the same port 8090 proxy?

Yes, you can route API endpoints, landing pages, and static assets through the same port 8090 proxy by mapping the new microservice with correct prefix stripping and POST forwarding rules.

Do I need to handle CORS preflight when proxying microservices?

Yes, you need to handle CORS preflight requests when proxying microservices to ensure cross-origin browser requests succeed, alongside cleaning hop-by-hop headers for reliable proxying.