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

Self Hosting Dahsboard #420

Open
sarpuser opened this issue Sep 26, 2024 · 4 comments
Open

Self Hosting Dahsboard #420

sarpuser opened this issue Sep 26, 2024 · 4 comments

Comments

@sarpuser
Copy link

sarpuser commented Sep 26, 2024

How can I self host the dashboard? I tried installing lighttpd and pointing the Document Root to dashboard/pages but that did not seem to work. Is there some other directory I should be pointing it to? I have never done any JS websites so not sure how they work without HTML files. Should I be using a different web server?

@Pettersen3008
Copy link

Pettersen3008 commented Oct 2, 2024

The dashboard itself is not a part of the Dockerfile so you would have to manually build the dashboard in a docker file or run it directly on the server you want to host the dashboard. Then you can point it to the given port 3001 in this case (usually 3000) (https://github.com/Lodestone-Team/lodestone/wiki/Getting-Started-for-Developers#setup-guide )

NB: This is not the way i think the application is intended to run by the maintainers. There are a way to build a next application with tauri (rust way of doing frontend) but i cant enough to help you with this.

@sentanos sentanos mentioned this issue Oct 15, 2024
4 tasks
@sentanos
Copy link

You can use the ghcr.io/lodestone-team/lodestone_dashboard Docker image and bind to port 80. For example:

docker run -d -p 3001:80 --name lodestone-dashboard ghcr.io/lodestone-team/lodestone_dashboard

And then the dashboard will be available at http://localhost:3001

@taedium8vitae
Copy link

Has anybody found a way to restrict the locally running dashboard to a single core ? There isn't much documentation available.

@WhySoBad
Copy link

Has anybody found a way to restrict the locally running dashboard to a single core ? There isn't much documentation available.

If you're using docker to serve the dashboard you can use the cpus property of docker:

  • --cpus=1 when using docker run
  • cpus: 1 in docker-compose.yml when using docker compose

You can read more about it here https://docs.docker.com/engine/containers/resource_constraints/#cpu

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

Successfully merging a pull request may close this issue.

5 participants