Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Update README to use new single weave launch command #1011

Closed

Conversation

awh
Copy link
Contributor

@awh awh commented Jun 25, 2015

Defer merge until #962 is released.

@awh awh mentioned this pull request Jun 25, 2015
@rade
Copy link
Member

rade commented Jun 25, 2015

I'd like to go a bit further here, if possible, and excise any mention of weaveDNS or the proxy from the README. On that note, I have been wondering whether we should rename weave proxy-[env|config] to just weave env|config (new issue, obviously).

@rade
Copy link
Member

rade commented Jun 25, 2015

This PR can become an accumulator for all the README changes that need to be merged at release time. I suggest we put the branch into the main repo, so its easier for everybody to work on it.

@awh
Copy link
Contributor Author

awh commented Jun 25, 2015

excise any mention of weaveDNS or the proxy

I'll give it a go.

On that note, I have been wondering whether we should rename weave proxy-[env|config]

Seems reasonable.

I suggest we put the branch into the main repo, so its easier for everybody to work on it.

Good idea. I'll have to close this PR and make a new one.

@awh awh closed this Jun 25, 2015
@awh awh deleted the weave_launch_all_the_things_readme branch June 25, 2015 13:52
@rade
Copy link
Member

rade commented Jun 25, 2015

I have raised #1014 for weave env|config.

@rade rade added this to the 1.1.0 milestone Jul 2, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants