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

LSF is not usable??? #6936

Open
Bradly-s opened this issue Jan 20, 2025 · 1 comment
Open

LSF is not usable??? #6936

Bradly-s opened this issue Jan 20, 2025 · 1 comment

Comments

@Bradly-s
Copy link

Bradly-s commented Jan 20, 2025

I run:

cd web
run yarn install --frozen-lockfile
run yarn lsf:watch
run yarn lsf:serve

open http://localhost:3000/,
The content I see is as follows, it is not usable?I can't see the entire LS project.

Image

@heidi-humansignal
Copy link
Collaborator

Hello,

Hello there,
Thanks for reaching out! When you run "yarn lsf:watch" and "yarn lsf:serve," you’re building and serving only the labeling interface (Label Studio Frontend, or LSF) in a standalone mode. By default, this doesn’t provide the full Label Studio experience. If you open http://localhost:3000 and see a mostly empty or “unusable” page, it’s likely because there’s no backend connection.
Below is the recommended way to see Label Studio fully in action:

  1. Start the Backend

In the main Label Studio folder (where “manage.py” lives), run:

python label_studio/manage.py runserver
This starts the backend on http://localhost:8080 by default.
2. Set Up Environment for the Frontend

Go to the “web” folder and create a file named “.env”. Add, for example:

FRONTEND_HMR=true
FRONTEND_HOSTNAME=http://localhost:8010
DJANGO_HOSTNAME=http://localhost:8080
(Adjust ports or addresses if you need something different.)
3. Install and Run the Full Dev Server

Still in the “web” folder:

yarn install --frozen-lockfile
yarn dev
This command bundles everything and runs the dev server. After it compiles, open http://localhost:8010 (or whatever port is shown) in your browser. You should now see a working Label Studio interface that’s actually connected to the backend.
If you only need to test or modify the standalone labeling interface for embedding somewhere else, then “lsf:watch” and “lsf:serve” can be enough. However, you typically still need a backend configuration to load data or display tasks properly in LSF.
Let me know if this helps or if you have any other questions!

Thank you,
Abu

Comment by Abubakar Saad
Workflow Run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants