Remove SSH refs
This commit is contained in:
parent
8885b9f98d
commit
ab7a956d01
|
@ -55,8 +55,7 @@ Commands:
|
||||||
stop: Stop a running container
|
stop: Stop a running container
|
||||||
restart: Restart a container
|
restart: Restart a container
|
||||||
destroy: Stop and remove a container
|
destroy: Stop and remove a container
|
||||||
enter: Use nsenter to enter a container
|
enter: Use docker exec to enter a container
|
||||||
ssh: Start a bash shell in a running container
|
|
||||||
logs: Docker logs for container
|
logs: Docker logs for container
|
||||||
bootstrap: Bootstrap a container for the config based on a template
|
bootstrap: Bootstrap a container for the config based on a template
|
||||||
rebuild: Rebuild a container (destroy old, bootstrap, start new)
|
rebuild: Rebuild a container (destroy old, bootstrap, start new)
|
||||||
|
@ -145,8 +144,6 @@ For a Discourse instance to function properly Email must be set up. Use the `SMT
|
||||||
|
|
||||||
View the container logs: `./launcher logs my_container`
|
View the container logs: `./launcher logs my_container`
|
||||||
|
|
||||||
You can ssh into your container using `./launcher ssh my_container`, we will automatically set up ssh access during bootstrap.
|
|
||||||
|
|
||||||
Spawn a shell inside your container using `./launcher enter my_container`. This is the most foolproof method if you have host root access.
|
Spawn a shell inside your container using `./launcher enter my_container`. This is the most foolproof method if you have host root access.
|
||||||
|
|
||||||
If you see network errors trying to retrieve code from `github.com` or `rubygems.org` try again - sometimes there are temporary interruptions and a retry is all it takes.
|
If you see network errors trying to retrieve code from `github.com` or `rubygems.org` try again - sometimes there are temporary interruptions and a retry is all it takes.
|
||||||
|
|
Loading…
Reference in New Issue