Hello,
Not sure if this should be suggested here or in kamal proxy first.
Now that the PR to support path based routing is landed + mine to support multi-path routing is getting submitted shortly, we can host "true" multi-stack apps where frontend goes one place, legacy api goes one place and main api goes one place etc.
This means that securing something like staging.myproduct.com with basic auth is non-trivial again.
I am thinking this can be a simple companion-config on the proxy like:
proxy:
other_stuff: ...
basic:
username: "asdf"
password: "password"
This could also pull from secrets like all other config can do.
On kamal-proxy side it should be enough to accept --basic-auth "asdf:password" as staged by the config parser.
Thoughts? If positive I can implement this.
Hello,
Not sure if this should be suggested here or in kamal proxy first.
Now that the PR to support path based routing is landed + mine to support multi-path routing is getting submitted shortly, we can host "true" multi-stack apps where frontend goes one place, legacy api goes one place and main api goes one place etc.
This means that securing something like staging.myproduct.com with basic auth is non-trivial again.
I am thinking this can be a simple companion-config on the proxy like:
This could also pull from secrets like all other config can do.
On kamal-proxy side it should be enough to accept --basic-auth "asdf:password" as staged by the config parser.
Thoughts? If positive I can implement this.