I used make-server to build server but its building it on localhost:9081 and returning with error code 404. I think some precise documentation for starting local server and setting up development-environment is needed.
having a similar issue, mesheryctl services are running on docker desktop but the UI server on localhost is not serving anything
Hello @anujagrawal. Can you please mention the steps that you took?
This will help people provide better and quick solutions.
I cloned the repo and installed the necessary dependencies and tried to use make server-local and it returned
fatal: No names found, cannot describe anything.
cd server; cd cmd; go clean; go mod tidy; \
BUILD="" \
PROVIDER_BASE_URLS="http://localhost:9876" \
PORT=9081 \
DEBUG=true \
ADAPTER_URLS="localhost:10000 localhost:10001 localhost:10012 localhost:10013" \
APP_PATH="./apps.json" \
KEYS_PATH="../../server/permissions/keys.csv" \
go run main.go error.go
^Cmake: *** [Makefile:81: server-local] Interrupt
So i did some internet serving and used this script
BUILD="" PROVIDER_BASE_URLS="http://localhost:9876" PORT=9081 DEBUG=true ADAPTER_URLS="localhost:10000 localhost:10001 localhost:10012 localhost:10013" APP_PATH="./apps.json" KEYS_PATH="../../server/permissions/keys.csv" go run main.go error.go
So the server is running up on 9081 but the page is returning with 404 and i think the server is trying to reach provider and adapters but they are unavailable. The UI or anything else is not visible on localhost.
I cloned the repo and installed the necessary dependencies and tried to use make server-local and it returned
fatal: No names found, cannot describe anything.
cd server; cd cmd; go clean; go mod tidy; \
BUILD="" \
PROVIDER_BASE_URLS="http://localhost:9876" \
PORT=9081 \
DEBUG=true \
ADAPTER_URLS="localhost:10000 localhost:10001 localhost:10012 localhost:10013" \
APP_PATH="./apps.json" \
KEYS_PATH="../../server/permissions/keys.csv" \
go run main.go error.go
^Cmake: *** [Makefile:81: server-local] Interrupt
So i did some internet surfing and used this script
BUILD="" PROVIDER_BASE_URLS="http://localhost:9876" PORT=9081 DEBUG=true ADAPTER_URLS="localhost:10000 localhost:10001 localhost:10012 localhost:10013" APP_PATH="./apps.json" KEYS_PATH="../../server/permissions/keys.csv" go run main.go error.go
So the server is running up on 9081 but the page is returning with 404 and i think the server is trying to reach provider and adapters but they are unavailable.
@Rudraksh_Tyagi
From your messages It seems to me you have not built meshery ui and provider ui yet.
Can you confirm if you have followed the steps mentioned here?
Yes i havenβt built the UI separately. I was looking to contribute to cypress and playwright e2e testing.
Regarding building Meshery Server, when you execute git describe --tags
does it respond with fatal: No names found, cannot describe anything.
?
Are you working with a shallow clone (git clone --depth=1
)? If so, try doing a full clone (git clone
) and trying make server
again.
Okay Thanks. Can i contribute a detailed docs on these subjects?
Yes, you can, @anujagrawal.
@Lee The files such ui/cypress/e2e/e2e/service_mesh_configuration_management_spec.js and integration/configuration_filters_spec.js and commented out. Are they commented out because they are made using Cypress? If yes, can i migrate it to Playwright?
I think someone already works with these issues
[CI]: add e2e test for navbar section by senthil-athiban Β· Pull Request #11406 Β· meshery/meshery (github.com)
From my understanding, Playwrights testing now has some manual processes to be done.
- The easy way to set up the server is by using MesheryCLI
mesheryctl system start
- Setup the environment variable
- Run the playwright test
@Jerens_Lensun what about migrating provider-ui/cypress tests to playwright?
@Jerens_Lensun The docker is running on port 3000. The mesheryctl system is started.
Env variables are set up in terminal and ~/.bashrc. Still running it gives
anuj_agrawal@Anuj:~/meshery-lfx/meshery/ui$ PW_TEST_CONNECT_WS_ENDPOINT=ws://localhost:3000/ npx playwright test
Running 38 tests using 1 worker
β 1 [setup] βΊ auth.setup.js:13:6 βΊ authenticate (14ms)
β 2 [setup] βΊ seedResources.setup.js:106:6 βΊ seed-resources (1.6s)
1) [setup] βΊ auth.setup.js:13:6 βΊ authenticate βββββββββββββββββββββββββββββββββββββββββββ
Error: browserType.connect: WebSocket error: connect ECONNREFUSED 127.0.0.1:3000
Call log:
- <ws connecting> ws://localhost:3000/
- <ws error> ws://localhost:3000/ error connect ECONNREFUSED 127.0.0.1:3000
- <ws connect error> ws://localhost:3000/ connect ECONNREFUSED 127.0.0.1:3000
- <ws disconnected> ws://localhost:3000/ code=1006 reason=
1 failed
[setup] βΊ auth.setup.js:13:6 βΊ authenticate ββββββββββββββββββββββββββββββββββββββββββββ
36 did not run
1 passed (4.3s)