Description

I start Filebrowser using:

filebrowser config init --commands 'ls unzip gzip gunzip tar' &&
filebrowser users add myadmin mypassword --lockPassword --perm.admin &&
filebrowser

Expected behaviour
The commands listed in the argument --commands are:

• present in the user configuration
• allowed and can be used in the UI

What is happening instead?
The commands listed in the argument --commands are:

• present in the user configuration (visible from the UI)
• not allowed and cannot be used in the UI

Additional context
It works if I copy the content of the field "Commands" from the UI, past the value in the same field (without any change), and save.
It works to if I use several --commands parameter, ex: --commands ls --commands unzip ... may be it is the way I should use it but in this case the documentation should be more precise on it, actually it says "a list of the commands a user can execute".

How to reproduce?
see description:

• init a config with default commands
• add a user
• start Filebrowser and try to use a command defined in the first step

Files
None