Currently, you need to look in the startup logs, or run jupyter notebook list within a container, to find out the token to log in.
It would be better if, like other recipes, we defined a Docker Secret for the password and had abra generate it. There's probably a way of setting an initial password using a jupyter command.
Maybe we want this behaviour in a separate compose.yml in case anyone wants to keep the token auth for any reason.
Currently, you need to look in the startup logs, or run `jupyter notebook list` within a container, to find out the token to log in.
It would be better if, like other recipes, we defined a Docker Secret for the password and had `abra` generate it. There's probably a way of setting an initial password using a `jupyter` command.
Maybe we want this behaviour in a separate `compose.yml` in case anyone wants to keep the token auth for any reason.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently, you need to look in the startup logs, or run
jupyter notebook listwithin a container, to find out the token to log in.It would be better if, like other recipes, we defined a Docker Secret for the password and had
abragenerate it. There's probably a way of setting an initial password using ajupytercommand.Maybe we want this behaviour in a separate
compose.ymlin case anyone wants to keep the token auth for any reason.