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
Original install method (e.g. download page, yum, from source, etc.): source
Describe the bug:
Upon trying to start with yarn start --no-basepath as per documentation I'm greeted with an error:
ERROR Extra serve options "--no-basepath" must have a value
Steps to reproduce:
clone repo & checkout v7.9.1
yarn kbn bootstrap
yarn start --no-basepath
Expected behavior:
Start's kibana in dev mode without a random app prefix as per documentation
Provide logs and/or server output (if relevant):
ERROR Extra serve options "--no-basepath" must have a value
Any additional context:
Using node 10.22.0
Tried running with:
yarn start --no-basepath=true
only to be greeted with:
log [13:58:24.918] [fatal][root] { Error: Unknown configuration key(s): "no-basepath". Check for spelling errors and ensure that expected plugins are installed.
at ensureValidConfiguration (private/kibana/src/core/server/legacy/config/ensure_valid_configuration.ts:41:11) code: 'InvalidConfig', processExitCode: 64, cause: undefined }
FATAL Error: Unknown configuration key(s): "no-basepath". Check for spelling errors and ensure that expected plugins are installed.
error Command failed with exit code 64.
The text was updated successfully, but these errors were encountered:
azasypkin
changed the title
"--no-basepath" flag not working
Change incorrect "--no-basepath" flag to "--no-base-path" in the developer documentation
Sep 28, 2020
Kibana version: 7.9.1
Original install method (e.g. download page, yum, from source, etc.): source
Describe the bug:
Upon trying to start with yarn start --no-basepath as per documentation I'm greeted with an error:
Steps to reproduce:
Expected behavior:
Start's kibana in dev mode without a random app prefix as per documentation
Provide logs and/or server output (if relevant):
Any additional context:
Using node 10.22.0
Tried running with:
only to be greeted with:
The text was updated successfully, but these errors were encountered: