You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While it may be useful to set both to the same value by default, the script should allow to set them to two different values, given that they have different purposes and formats.
Currently the script uses the same NAME variable for both, so the container name set via -n command line argument is actually replaced by what it's set into the env/* configuration file.
The text was updated successfully, but these errors were encountered:
Alright, that makes sense. We actually had two different parameters for the node name and container name but I decided to simplify it.
However, with the next update of this repo I’ll keep the default value of the container name to be the same as the node name but re-introduce container name as a separate, optional argument.
While it may be useful to set both to the same value by default, the script should allow to set them to two different values, given that they have different purposes and formats.
Currently the script uses the same
NAME
variable for both, so the container name set via-n
command line argument is actually replaced by what it's set into theenv/*
configuration file.The text was updated successfully, but these errors were encountered: