Docker and `AUTH=false` doesn't work #4

New issue

Closed

opened 2024-07-15 00:52:00 -07:00 by NamesMT · 3 comments

NamesMT commented

2024-07-15 00:52:00 -07:00

(Migrated from github.com)

I tried all variances of using AUTH=false, by docker-compose.yaml, inline docker run command, S3 storage, normal storage,... but it does not seems to work.
Setting AUTH_USERNAME or using .htpasswd does work normally.

I tried all variances of using `AUTH=false`, by `docker-compose.yaml`, inline docker run command, S3 storage, normal storage,... but it does not seems to work. Setting `AUTH_USERNAME` or using `.htpasswd` does work normally.

hperrin commented

2024-10-12 12:39:02 -07:00

(Migrated from github.com)

I figured it out. It is reading the env var, but commander sets the option to true if there is no --no-auth argument. Arguments take precedence over env vars, so commander's prop ends up being the value. I need to figure out how to detect that there wasn't an argument, and commander is just setting the default.

I figured it out. It is reading the env var, but `commander` sets the option to true if there is no `--no-auth` argument. Arguments take precedence over env vars, so commander's prop ends up being the value. I need to figure out how to detect that there wasn't an argument, and commander is just setting the default.

hperrin commented

2024-10-12 12:49:01 -07:00

(Migrated from github.com)

This actually affects all boolean env vars that default to true (AUTH, NYMPH_REGISTRATION, and UPDATE_CHECK).

hperrin commented

2024-10-12 13:08:23 -07:00

(Migrated from github.com)

This fix has been pushed up to Docker now.