Tailscale x Caddy 조합으로 VPS 웹 접속 열기 tl:dr; Caddy를 다음과 같이 설정: example.christracy.com reverse_proxy 100.85.190.10:80 # tailscale IP christracy.com/posts/using-t…

معرفی کتاب NGINX Cookbook این کتاب یک رفرنس عالی برای یادگیری کانفیگ و مدیریت انجین‌ایکس هست؛ وب‌سروری قدرتمند برای مدیریت ترافیک و ریورس پراکسی. youtube.com/watch?v=brGNfaxt… #معرفیـکتاب #علومـکامپیوتر #مهندسیـنرمـافزار #nginx #reverse_proxy #devdrug

Was reading some docs. Love how the caddy section is just `reverse_proxy http://localhost:8080` @caddyserver 🥰 neko.m1k1o.net/docs/v3/rever…

Install: caddyserver.com/docs/install Edit /etc/caddy/Caddyfile domain.one { reverse_proxy localhost:8080 } https://domain.two { file_server /path/to/files } Restart caddy

Caddy のドキュメントを見たところ、logrotate も自動で行われるみたい。しばらく様子を見てみる。 #godot #godotengine #gamedev #indiedev #indiegame #Networking #WebSocket #caddy #reverse_proxy

Caddy でアクセスログを出力できた。ログは、Godot で WebエクスポートしたゲームクライアントからWebSocket通信したもの。WebSocket は通信の仕様的に切断時にしか出力されない。 #godot #godotengine #gamedev #indiedev #indiegame #Networking #WebSocket #caddy #reverse_proxy

@caddyserver is a no-brainer 🧠 choice for securing (https reverse_proxy) self-hosted SaaS deployment at this point. No longer have to wrestle with @letsencrypt certbot and @nginx. It just works! ✨

様々な情報を雑に捻じ曲げながらreverse_proxyをするのに便利。 Dockerイメージも openresty/openresty にて配布されている。

For Django, it's just reverse_proxy to your uvicorn or whatever the new hotness in Python-land. For WordPress & Laravel we have caddyserver.com/docs/caddyfi… (or use FrankenPHP). For nextcloud there's the wiki on the forums. For Ruby I assume just reverse_proxy as well (I'm not a user)

Pues este fin hice deploy de la aplicación que voy a desarrollar para el curso de Udemy usando lo mas sencillo: ec2, Caddy como reverse_proxy, e instalando postgresql en el mismo servidor (y se que esta RDS) pero para tener la DB gratis para el curso, y enseñar las dos opciones.

Use @caddyserver (designed by yours truly): reverse_proxy backend1:1234 backend2:1234 ^ That's it. Automatic HTTPS for your site too.

Got this working via reverse proxying using @caddyserver! Caddyfile: ollama.test { tls internal reverse_proxy 127.0.0.1:11434 } and in /etc/hosts: ollama.test 127.0.0.1 And `GET https://ollama.test/v1/chat/completions` works perfectly in Safari.

I will say, this is one of the first things I did, and it made me happy: myapp.localhost { tls internal log stdout reverse_proxy /api/* localhost:{$PORT:3000} reverse_proxy localhost:{$VITE_PORT} } I have a bun server and a vite SPA

It turns out i've been overcomplicating things. This is how you manage SSL certificates, forward http to https, and handle traffic as a reverse proxy: sudo vim /etc/caddy/Caddyfile my.domain { reverse_proxy localhost:3000 } That's it, nothing else. Thank you @caddyserver

開発環境でフロントとバックエンドを毎回HTTPS化するの面倒だなー。 と、思ってたらcaddyなるもの発見した。 こんな感じで設定ファイルを書いて django.local { reverse_proxy localhost:8000 } nuxt.local { reverse_proxy localhost:3000 } caddy run を実行するだけでHTTPS化できる

that's one of the weak points of CaddyServer, not great docs, but the upside are sooo good it is worth it. The best is just to learn from examples. Here's one example from our own servers We have the /api/ that is connected to a unix sock, and we have media for uploaded content and app for the application (cors) { header Access-Control-Allow-Origin "*" header Access-Control-Request-Method GET } goleko.com { handle /api/* { reverse_proxy unix//home/cq0/gunicorn.sock encode zstd gzip request_body { max_size 50MB } } handle_path /media* { request_body { max_size 20MB } import cors encode zstd gzip root * /home/cq0/data/media file_server } handle_path /app* { request_body { max_size 20MB } import cors encode zstd gzip try_files {path} /index.html root * /home/cq0/data/fe_app/app file_server } handle { request_body { max_size 20MB } encode zstd gzip import cors root * /home/cq0/data/fe_app file_server } }

To add onto that - you can use Swoole if you want, just use Caddy's reverse_proxy to send HTTP requests to your Swoole app. There's nothing special to do or document in Caddy there.

you need not to know the IP, you can reverse proxy on the domain also. handle @client_domains { reverse_proxy verceldomain.app }