redbeat VS Caddy

afaik you cant dynamically create scheduled tasks - but i was able to achieve this with redbeat. curious to see what more experienced ppl have to say as well.

of course it does. Appliku out of the box provides a way to provision redis and rabbmitmq.

I have yet to write a tutorial about celery.

To specify processes to run you use Procfile. Specify your celery commands and enable them in Process tab in Appliku interface.

In order to have celery beat working you should use redbeat: https://github.com/sibson/redbeat

Other than that – no specific requirements. Drop me a line in contacts on our site if you need any help. Or in our Discord Community: https://appliku.com/discord

The secret is Caddy. Unlike Nginx, Caddy handles SSL automatically — it requests certificates from Let's Encrypt and renews them without any configuration. The entire reverse proxy config is 3 lines:

We recommend pre-compressing assets during your build pipeline using the official https://github.com/google/brotli CLI tool, which allows you to use higher compression levels (9-11) without adding latency to requests. Our benchmarks show that pre-compressed brotli assets at level 11 are 22% smaller than on-the-fly brotli level 6, with zero runtime overhead. For teams serving more than 100GB of static assets monthly, this optimization alone can save $500+ in bandwidth costs. Always validate compression ratios with the https://github.com/caddyserver/caddy built-in debug logs or Nginx’s $brotli_ratio variable to ensure your compression settings are effective. This tip is especially valuable for teams with mobile-heavy user bases, where reduced payload sizes directly correlate to lower bounce rates and higher conversion.

This tutorial walks you through setting up a simple Docker Compose project that serves two Node web servers over HTTPS using Caddy as a reverse proxy. You will learn how to use mkcert to generate wildcard certificates and the minimal configuration needed in the Caddyfile and docker-compose.yml to get it all working.

Mercure is a real-time push protocol built on server-sent events (SSE). It ships as a standalone binary that embeds its own Caddy server. If you already run Caddy as your web server, you now have two Caddy processes fighting over ports. This post covers how to deploy both on the same VPS using Ansible, with solutions for every gotcha that came up.

Caddy is a modern web server with automatic HTTPS. It obtains and renews TLS certificates from Let's Encrypt without any configuration.

Caddy (v2.9) is a modern web server and reverse proxy written in Go. Its defining feature is automatic HTTPS — point it at a domain name and it handles certificate provisioning and renewal without any configuration. Routes are defined in a Caddyfile, a human-readable config format that replaces Nginx's verbose blocks with minimal syntax.

Thanks for sharing this, we like it a lot. Mohammed Al-Sahaf implemented this for us so that releases can be made by a quorum of maintainers rather than being blocked by me every time.

Here's the first release done with it: https://github.com/caddyserver/caddy/releases/tag/v2.11.0-be...

And you can see the PR flow where the action happens: https://github.com/caddyserver/caddy/pull/7383

Add a reverse proxy service. The reverse proxy is necessary in production, because it handles SSL termination and forwards requests to your Django app running in Docker. Most reverse proxies can also do some other cool tricks, like caching requests, compressing responses, and more. I compared 5 different reverse proxies in this post. One of the simplest is Caddy, which comes with automatic SSL via Let's Encrypt and is very easy to configure.

I'm building this for myself after not being able to find anything useful enough for me (GoAccess [0] gets very close, but it doesn't have a nice HTML output with graphs I'd like, and it's hard to analyze substantial amounts of requests/data).

If there's anyone interested in trying something like this (or you know of a better tool), please reach out (you can find my email in my website, which is in my profile, or just `me[at][my username].com`).

Oh, and because caddy might mean a few different things, I'm talking about the amazing web server [1].

[0] https://goaccess.io

[1] https://caddyserver.com/