Merge lp:~kim-phillips/lava-scheduler/updates into lp:lava-scheduler
Proposed by
Kim Phillips
Status: | Needs review |
---|---|
Proposed branch: | lp:~kim-phillips/lava-scheduler/updates |
Merge into: | lp:lava-scheduler |
Diff against target: |
29 lines (+5/-3) 1 file modified
doc/usage.rst (+5/-3) |
To merge this branch: | bzr merge lp:~kim-phillips/lava-scheduler/updates |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Tyler Baker | Pending | ||
Alan Bennett | Pending | ||
Review via email: mp+164274@code.launchpad.net |
Commit message
doc/usage.rst: documentation updates
- include lava-server/ in the URL paths
- make URLs consistently use https: and include user@
- mention trailing slashes are required
Description of the change
doc/usage.rst: documentation updates
- include lava-server/ in the URL paths
- make URLs consistently use https: and include user@
- mention trailing slashes are required
To post a comment you must log in.
Unmerged revisions
- 247. By Kim Phillips
-
doc/usage.rst: documentation updates
- include lava-server/ in the URL paths
- make URLs consistently use https: and include user@
- mention trailing slashes are required
validation. linaro. org happens to be located in a legacy location /lava-server/ RPC2/
- https://<email address hidden>
The default location for a new lava install would be:
- https://<email address hidden>/RPC2/
However, the important note is that the user needs to point the browser to the lava installation URL.
Perhaps we need to mention all three cases? linaro. org
1. legacy installation path for validation.
2. current installation path for new lava installs
3. custom vhost configurations