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

Idea: make monerod-gui available in the web browser #9

Open
hundehausen opened this issue Jan 5, 2025 · 1 comment
Open

Idea: make monerod-gui available in the web browser #9

hundehausen opened this issue Jan 5, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@hundehausen
Copy link

Is your feature request related to a problem? Please describe.
Monerod GUI is a desktop application for managing a local monero node on a desktop computer. It could be that people would also want to deploy monerod-gui along with monerod on a server on the local network and then they could remote manage it with monerod-gui in the browser.

Describe the solution you'd like
monerod-gui could run in a docker container with a web server that connects to monerod over the docker network or local network.

Describe alternatives you've considered
none

Additional context
That way we could also think adding monerod-gui to monero-suite.

@everoddandeven everoddandeven added the enhancement New feature or request label Jan 5, 2025
@everoddandeven
Copy link
Owner

Hi @hundehausen thanks for opening the issue! This idea falls under the remote management of a node from what I understand. The goal would therefore be to manage a remote node using monerod-gui.

The difficulty in making monerod-gui a deployable application on a web server is that most of the features have been developed having electron as a base, which allows me to interact with the monerod executable in the local file system electron.service.ts . Making monerod-gui deployable on a web server means having to provide an additional support server service that implements all the features currently supported by electron. A code refactory would then be necessary and an abstract api would be available that depending on the environment makes the necessary calls to electron or the support service.

My idea was instead to use the SSH protocol to connect to a remote monerod server and interact with the monerod service/executable, again a refactory and an api will be necessary. In this case, the web server deployment seems to be a less attractive solution, but what do you think?

I like the idea of ​​providing a support service anyway. I'm thinking about creating a MoneroRestServer that uses monero-java to provide wallet and daemon services through a simplified and powerful API.

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

No branches or pull requests

2 participants