-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Document what can be tested in Testing with Vagrant #76
Comments
To ssh you can just run vagrant: Here are some default ports and the location where they are defined:
The Vagrantfile, expose this ports:
Could not find where the load_balancer default front end is defined as a default, but found this document: http://plone-ansible-playbook.readthedocs.io/en/latest/load_balancer.html |
In the multiserver example first of all the initial provisioning is not tested if it fails at all. See my ticket: #113 Therefore a later failing does not give any hint. If you customize the example everything in the tests needs to be adjusted (right?) |
@stevepiercy I think this PR #118 addresses your main point If you think the |
There is no main point, but several interrelated points. Reopening. |
I added @ramiroluz 's helpful port forwarding info |
I added some comments to the commit. I could not submit them to request changes in a review. |
It's not clear what can be tested under Testing with Vagrant. It would be good to set the user expectation so they don't spend time trying to get something to work that will not, and to improve documentation for things that do work, including links to settings in this repo and Plone docs.
The running of the playbook itself is one test.
It took a while to figure out how to SSH in. I got some settings from
vbox_host.cfg
. Eventually I figured out that this works:ssh -i /path/to/virtualbox/private_key ubuntu@127.0.0.1 -p2222
I tried all the suggested ports over HTTP:
http://127.0.0.1:1080 (web server/virtual hosting. Links and subrequests to assets (JS, CSS, images) won't work. If there is a known fix or workaround, it would be good to document that.)
http://127.0.0.1:2080 (haproxy stats page?)
http://127.0.0.1:7081 ("Plone is up and running" page)
http://127.0.0.1: 9080 (webdav?)
http://127.0.0.1: 5949 (munin?)
Is there anything that can be tested, and if so through what method?
I volunteer to do any documentation for this.
The text was updated successfully, but these errors were encountered: