HN user

martianE

33 karma
Posts2
Comments9
View on HN

Our product assumes familiarity with Caddy/Nginx -- we'll make it more accessible soon. We give you global anycast nodes on it and you're in full control of the config (they can be edited on the website), so anything you can have in a Caddy config can be used on Novanode.

The managed bits are the certs/configs/failover so that you don't need to be concerned about that.

Though for a single VPS instance it could makes sense to just host your own caddy on that node. If you need global distribution Novanode is a good answer.

Our goal is actually not to hide the configs behind a bunch of partial UI elements you get full control of your proxy. All your caddy configs should work out of the box. For SSL termination we use acme and you can use the dns method (let us know if you dns provider isn't in the plugins and we'll add it)

Pretty much the only thing we add is a storage layer for your certs so you avoid the acme rate limit for multi-region deployments

For high-availability deployments, we leverage Fly.io's global Anycast network and DNS-based health checks. When a machine in region A goes offline, Fly's Anycast routing automatically directs traffic to healthy machines in other regions without manual intervention.

For intra-region redundancy, we deploy 2 nodes per region in HA mode. If one node fails, traffic is seamlessly routed to the other node in the same region through Fly.io's internal load balancing. This provides N+1 redundancy within each region, ensuring service continuity even during single-node failures.

I cannot stress this enough: write good code! Any decent code editor now jumps you to the source of the code you're calling allowing you to quickly see what the code does, what parameters are needed, etc.

In fact the best documentation I've seen (say flask, django) most of the documentation acts as support for reading the code.