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

clarify how to enable VNC #18

Merged
merged 3 commits into from
Feb 3, 2023
Merged

clarify how to enable VNC #18

merged 3 commits into from
Feb 3, 2023

Conversation

ptmkenny
Copy link
Contributor

This may be a rookie mistake, but I had trouble enabling VNC because I uncommented the "5900:5900" line and missed uncommenting "ports:". Another reason I missed this is that the indentation is wrong; "ports:" has to be at the level of "external_links". So I edited the comment to make it more clear about how to enable port 5900.

Copy link
Member

@rfay rfay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see anything wrong with this change, but could you explain why you would use this instead of browser on https://[DDEV SITE URL]:7900? If there is significant value, please also add to the README explaining this approach. Note that when you start using ports only one project at a time can be running with port 5900.

@ptmkenny
Copy link
Contributor Author

@rfay Ok, I updated the README with some basic guidelines that I hope are pretty easy to follow and non-controversial.

Copy link
Member

@rfay rfay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks!

@tyler36
Copy link
Collaborator

tyler36 commented Jan 23, 2023

Are there any additional steps needed?

I can visit https://[project_name]:7900/ and login with secret. I can run my funcationJavascript tests, which pass/fail as expected but the https://[project_name]:7900/ page only shows the "Selenium Grid" logo and title.

selenium-chrome

@ptmkenny
Copy link
Contributor Author

@tyler36 There shouldn't be any additional setup required. Make sure you aren't running your tests headless. The tests that are shown are those that actually require the Chromium browser to be opened to run the tests, so if the tests are running headless in the background, they won't be shown.

@tyler36
Copy link
Collaborator

tyler36 commented Jan 23, 2023

@ptmkenny Thanks for the suggestion.

By removing \"--headless\" from .ddev/config.selenium-standalone-chrome.yaml, and restarting DDEV to apply the updated config, I was able to watch the tests.


On your host, browse to https://[DDEV SITE URL]:7900 (password: `secret`) to watch tests run with noVNC (neat!).

This is a no-configuration solution that enables you to quickly see what is going on with your tests.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Considering we need to make configuration changes and restart DDEV, I'm not so sure about the wording here. 🤷

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I didn't realize that --headless is set in the YAML file, so there should probably be a section on how and why to disable headless as well. What's the reason for setting --headless as a default in the first place? Is it just speed?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I imaging there would be memory savings from using --headless, which might be more important when running on CI.

Note there are 2 references, one for Mink tests and one forr DTT tests.

@weitzman , are there issues removing this as the default?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm able to watch just fine with the existing configuration.

@rfay
Copy link
Member

rfay commented Feb 3, 2023

Ping @weitzman before this gets too stale.

@weitzman weitzman merged commit 755b854 into ddev:main Feb 3, 2023
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 this pull request may close these issues.

5 participants