update readme to take advantage of new-project #1104
Conversation
|
In response to #999 (comment) |
examples/sample-app/README.md
Outdated
There was a problem hiding this comment.
nest this under the "Optional: View in web console" step? Just so they can skip it if they don't care about the web browser
There was a problem hiding this comment.
This step is labelled optional. You can look at two times. Once to see the docker registry deployed and once to see the rest of the test resources created.
|
Remove the project.json, and the reference to downloading it in container-setup.md? |
|
not sure how aggressive we're being with examples following best practices (e.g. "your script that used project.json will now break because that's not how we want you creating it"). @bparees, you have an opinion? |
|
@liggitt yeah we should try to keep the readme following best practices since it's probably something a lot of people will end up monkey-see-monkey-doing. |
|
@liggitt updated for comments. |
deads2k
force-pushed
the
deads-update-readme
branch
from
2aca180 to
d1704f6
Compare
|
LGTM, squash and merge |
deads2k
force-pushed
the
deads-update-readme
branch
from
d1704f6 to
3079d08
Compare
|
[merge] |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_openshift3/1016/) (Image: devenv-fedora_869) |
|
Evaluated for origin up to 3079d08 |
Merged by openshift-bot
4 participants
Updates to the sample app readme that add instructions for properly authorizing a user to see a project and make use of the new-project command.
/cc @smarterclayton @liggitt