-
Notifications
You must be signed in to change notification settings - Fork 80
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
Steps to run on remote server #331
Comments
This increasingly looks like it will not be just a compilation of steps; instead, it will require some alterations to the codebase to make things work properly. More specifically, running "make launch" on a terminal connected to another VM does launch seemingly all of the terminals. They are not visible on the original VM (the one on which ssh is running) but are visible on the VM to which one is connecting, but none of the GUI stuff (COSMOS, the 42 GUI, or any such thing) appears anywhere. "make stop" does precisely what it is supposed to do, and does not send any errors. |
A user has reported that when running xquartz on a Mac host to connect to a remote Ubuntu server issues exist with forwarding the displays. Need to document the recommended setup steps to get this working.
Additionally it may be bad practice to call xhost in the launch script and another means should be leveraged to ensure authentication works as expected.
The text was updated successfully, but these errors were encountered: