Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After clone this object, open it use the 'npm run server' command, but localhost page show 'Cannot GET /' #2516

Closed
WeldonLei opened this issue Mar 12, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@WeldonLei
Copy link

WeldonLei commented Mar 12, 2024

npm run serve

......
Building libresign 9.0.0

[webpack-dev-server] Project is running at:
[webpack-dev-server] Loopback: http://localhost:3000/
[webpack-dev-server] On Your Network (IPv4): http://...:3000/
[webpack-dev-server] On Your Network (IPv6): http://*****************:3000/
[webpack-dev-server] Content not from webpack is served from 'E:\workplace\libresign\public' directory
......

Is it to run the php file? How to run it?

@WeldonLei WeldonLei added the bug Something isn't working label Mar 12, 2024
@github-project-automation github-project-automation bot moved this to 0. Needs triage in Roadmap Mar 12, 2024
@vitormattos
Copy link
Member

Hi @WeldonLei

To setup the development environment you need to follow my development instructions from here:
https://github.com/LibreSign/libresign/blob/main/CONTRIBUTING.md#developing-for-libresign
And you also can found the Nextcloud official instructions about development enviroment here:
https://docs.nextcloud.com/server/latest/developer_manual/getting_started/devenv.html

Is necessary to build and install LibreSign on Nextcloud server. You need to start Nextcloud server in your environment first. LibreSign is an app that the API side works on Nextcloud server.

Other important point is that Nextcloud haven't support to run on Windows systems, even if it is in containers.

About the port 3000, this port is only a socket to be possible use hot reload and get the frontend updated after do frontend changes.

This is not a bug.

@vitormattos
Copy link
Member

Closing this issue due to lack of interaction after 1 week and because it's actually not an issue.

@github-project-automation github-project-automation bot moved this from 0. Needs triage to 4. to release in Roadmap Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

2 participants