Skip to content

Fix typo and add explicit documentation on how to update the server #213

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 14, 2019
Merged

Fix typo and add explicit documentation on how to update the server #213

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/Basics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ Config file has the following structure:
"image": "",
// image file to load image from
// exoframe will load given tar file into docker daemon before
// execting image deployment
// executing image deployment
"imageFile": "",
// basic auth, [optional]
// this field allows you to have basic auth to access your deployed service
Expand All @@ -159,7 +159,7 @@ Exoframe stores its config in `~/.exoframe/cli.config.yml`.
Currently it contains list of endpoint URLs with associated usernames and authentication tokens:

```yaml
endpoint: 'http://localhost:8080' # your endpoint URL, defaults to localhost
endpoint: "http://localhost:8080" # your endpoint URL, defaults to localhost
```

## SSH key auth
Expand All @@ -186,3 +186,7 @@ The way it works is quite simple:
3. Exoframe removes the old running deployments for current project

This can be used together with deployment tokens to achieve simple continuous deployment for your projects.

### Updating the server

The server can simply be updated by invoking `exoframe update server`.