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

Run Backend / Frontend on separate hosts #103

Open
marshalleq opened this issue Jul 2, 2023 · 2 comments
Open

Run Backend / Frontend on separate hosts #103

marshalleq opened this issue Jul 2, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@marshalleq
Copy link

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.
I have a powerful linux / windows machine that has a nice grunty GPU in it etc. As is typical of these machines, to run well they have lots of noisy fans - even if you use something like Noctua, it's still noisy. I also have a really modern apple silicon mac. it's really really quiet. It would be fantastic to get the best of both worlds by being able to run the backend that does all the GPU crunching on the linux machine and the frontend on the mac machine. This might already be possible, but I didn't see it in the guide and while the mac does connect to the linux machine's front end GUI, it complains that the backend isn't running - even though it is. I suspect not hard to make this feature happen.

Describe alternatives you've considered
Running it all on the mac. Assuming it uses the Mac's new GPU - it's still not as fast as the NVIDIA 4090 in my linux machine.

Additional context
Add any other context or screenshots about the feature request here.

@marshalleq marshalleq added the enhancement New feature or request label Jul 2, 2023
@marshalleq
Copy link
Author

marshalleq commented Jul 2, 2023

Just adding a note that also attempting to run it on a Mac, port 5000 is already in use as a default port in use for a few years now. Apparently it's airplay which could be disabled probably but of course I should be able to map a different port, but would be good to sort it out permanently in the build.

@marshalleq
Copy link
Author

In case someone comes googling here, this was how I got it going.

Just an update the fix was ultimately to change in three places:

In docker compose.yml
ports:

Then finally it works. This works well on a Mac.

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

1 participant