Caddy JSON config - subroutes, ids and directive order

[Mohammed90 (Mohammed Al Sahaf)]

@makinghappen

Sometimes I need to add a new subroute, which must be above other subroutes(as the path length based route ordering does not work on JSON config level), is there a way to specify order, or all subroutes must be deleted, and then readded in a correct order?

If you’re pre-pending, use PUT with the path traversal ends with the index at which you want the insert to start. So if you’re prepending to the beginning of the array, use PUT and traversal of index /0. Link to the PUT docs:

API - Caddy Documentation

@makinghappen

Is it a good idea to group by domain on a route level to avoid any collisions, when modifying one domain would affect other?

I guess? It depends on your strict routing and matching criteria. If domain name is your reference, then, yes, use domain name grouping. I’ve touched on this aspect here:

Separation of Duty with Caddy Remote Administration

Assuming your organization has two different teams who are responsible for two different subdomains besides the main domain name, you would have a Caddyfile that is more of less as follows: example.com { root sites/root file_server } team-1.example.com { root sites/team-1 file_server } team-2.example.com { root sites/team-2 file_server } If team-1 would like to update their service to be proxying to an upstream rather than serving files, they would have to reach the singular team who i…