Automatic HTTPS
Caddy automatically handles HTTPS by obtaining and renewing certificates from Let’s Encrypt, simplifying the process of securing web applications.
Ease of Configuration
Caddy uses a straightforward configuration file (Caddyfile) that is easier to write and understand compared to other web servers like Nginx or Apache.
Cross-Platform
Caddy is designed to run efficiently on virtually any platform, including Windows, macOS, Linux, and Docker, giving it great flexibility for deployment.
Built-in Reverse Proxy
Caddy includes built-in support for reverse proxy functionality, which can easily be configured to distribute load among multiple servers.
Extensible
Caddy supports plugins for additional features, allowing users to extend its functionality without compromising its core simplicity.
Integrated Logging and Metrics
Caddy includes integrated logging and monitoring capabilities, which make it easier to maintain and debug the server without additional tools.
Active Community and Support
Caddy has an active community and is well-supported with extensive documentation, which helps new users get up to speed quickly and troubleshoot issues effectively.
Not sure about lesser known but my top tools are: – Caddy server (Auto SSL, Dead simple Reverse Proxy) [0] – mkcert(local SSL) [1] – AWS Global Accelerator [2] (Static IP, Route traffic based on location) [2] [0] https://caddyserver.com/ [1] https://github.com/FiloSottile/mkcert.
– Source: Hacker News
/
7 days ago
I recommend checking out [Caddy](https://caddyserver.com/), which replaces both Nginx and Certbot in this setup. [Tailscale](https://tailscale.com/) can remove the need to open port 22 to the world, but I wouldn’t rely on it unless your VPS provider has a way to access the server console in case of configuration mistakes.
– Source: Hacker News
/
28 days ago
A lot of the things you described sound like caddy? [1] [1] https://caddyserver.com/.
– Source: Hacker News
/
about 2 months ago
Caddy [1] can act as a static file server that will default to HTTP 2 if all parties support it. No configuration required. If you allow UDP connections in your firewall, it will upgrade to HTTP 3 automagically as well. I highly recommend it [1] https://caddyserver.com/.
– Source: Hacker News
/
about 2 months ago
After testing the dockerization, the next thing to work on was the Load Balancer. There are a number of tools to choose from, but I chose to work with Caddy.
– Source: dev.to
/
about 2 months ago
It’s a glorified local setup, running in a cloud free tier. – Oracle Cloud Free Tier[1] for a Ubuntu VPS (4 ARM cores, 24 GB RAM). Surprisingly pleasant and reliable, given who’s offering and for how much ($0). It used to be a FreeBSD VPS on DigitalOcean, until they kept screwing up their FreeBSD support and bricking my machines. – Caddy[2] web server with Let’s Encrypt certificates, working as reverse proxy. – A…
– Source: Hacker News
/
3 months ago
These projects use Caddy as my local development server, Dart Sass for converting my Sass files to CSS, elm, elm-format, elm-optimize-level-2, elm-review, elm-test (only in Calculator), ShellCheck to find bugs in my shell scripts, and Terser to mangle and compress JavaScript code.
– Source: dev.to
/
5 months ago
It uses devbox, Elm 0.19.1, the latest Elm packages (in particular elm/http 2.0.0), elm-review, Caddy, a sprinkle of Dart Sass, and a handful of Bash scripts (one of them being a deployment script). It uses elm test and features tests for key data structures.
– Source: dev.to
/
5 months ago
However, it’s very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:.
– Source: dev.to
/
7 months ago
Caddy [1] is a single binary. It is not minimal, but the size difference is barely noticeable. serve also comes to mind. If you have node installed, `npx serve .` does exactly that. There are a few go projects that fit your description, none of them very popular, probably because they end up being a 20-line wrapper around http frameworks just like this one. [1] https://caddyserver.com/.
– Source: Hacker News
/
6 months ago
Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using…
– Source: dev.to
/
6 months ago
So I dug a little deeper and came across this gem: Caddy. Caddy is this fantastic, extensible, cross-platform, open-source web server that’s written in Go. The best part? It comes with automatic HTTPS. It basically condenses all the work our scripts and manual maintenance were doing into just 4-5 lines of config. So, stick around and I’ll walk you through how to set up an automatic SSL solution with Caddy, Docker…
– Source: dev.to
/
7 months ago
Let’s use Caddy which can act as reverse-proxy with automatic HTTPS coverage.
– Source: dev.to
/
7 months ago
One of the most heavily used Russian software projects on the internet https://www.nginx.com/blog/do-svidaniya-igor-thank-you-for-nginx/ but it’s only marginally more modern than Apache httpd. In light of recently announced nginx memory-safety vulnerabilities I’d suggest migrating to Caddy https://caddyserver.com/.
– Source: Hacker News
/
7 months ago
Maybe take a look at Caddy (https://caddyserver.com/).
– Source: Hacker News
/
7 months ago
My preferred solution is using Caddy. This will resolve the networking issues, work as a great reverse proxy, and takes care of the whole SSL process for us. We can follow the install instructions from their documentation and run these five commands:.
– Source: dev.to
/
8 months ago
I empathize with the author and found the post to be a interesting and concrete example of what it’s _actually like_ to try to publish a blog to Mastodon, which is something that I have thought about and read about in abstract. So, thank you sir for writing this up. One thing to consider would be to try to use Caddy [0], or a tool like localias [1], as a local https proxy. You might be able to run both the…
– Source: Hacker News
/
9 months ago
Docker networking usually stops on your machine. If you want to expose your apps to the internet you can either use a reverse-proxy like Caddy or a reverse-tunneling tool like ngrok or Livecycle. Tools like caddy are great for production-ready and deployed apps, while something like Livecycle is more for a prototyping/collaboration use-case. While this is of course not necessary, at some point you will have to…
– Source: dev.to
/
9 months ago
When I run nix-shell at the root of the project it puts me in a Nix shell that contains, among other programs, caddy and shellcheck. Notice that in the shellHook I add the project’s shell scripts to the PATH. So once I’m in the Nix shell I can, among other things:.
– Source: dev.to
/
9 months ago
Fun fact, the website is “dynamically static”, it’s just markdown files being processed and rendered by Caddy itself using https://caddyserver.com/docs/caddyfile/directives/templates. It’s also how the https://caddyserver.com/ is built as well. Also includes syntax highlighting for Caddyfile config, using a library called Chroma; I wrote the Caddyfile lexer myself a while back! I think it’s pretty neat that Caddy…
Source:
10 months ago
Caddy is a web server like nginx. The biggest advandage of Caddy over nginx is, that it handles HTTPS automatically. You can find the script to install Caddy in their documentation.
– Source: dev.to
/
11 months ago