Skip to content

Commit

Permalink
Update references to Staging in docs (#745)
Browse files Browse the repository at this point in the history
* Update references to Staging in docs

There seems to be some documentation drift between "development" and "staging" environments.

* Change all occurrences of "development" to "staging" when it comes to
the default `up` commands.

* add .com to up example url
  • Loading branch information
harlow authored and tj committed Jan 1, 2019
1 parent ba77a21 commit d273f38
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions docs/06-commands.md
Original file line number Diff line number Diff line change
Expand Up @@ -414,19 +414,19 @@ Flags:

### Examples

Show the development endpoint.
Show the staging endpoint.

```
$ up url
```

Open the development endpoint in the browser.
Open the staging endpoint in the browser.

```
$ up url --open
```

Copy the development endpoint to the clipboard.
Copy the staging endpoint to the clipboard.

```
$ up url --copy
Expand Down
6 changes: 3 additions & 3 deletions docs/07-guides.md
Original file line number Diff line number Diff line change
Expand Up @@ -228,15 +228,15 @@ You should see "Hello World from production" and "Hello World from staging".

Now that you have an application deployed, you probably want a fancy custom domain for it right? You can map these using the `stages` and `domain` properties.

Here we let Up know that we want `up-example.com` for production and `dev.up-example` for staging.
Here we let Up know that we want `up-example.com` for production and `stage.up-example.com` for staging.

```json
{
"name": "up-example",
"profile": "up-tobi",
"stages": {
"staging": {
"domain": "dev.up-example.com"
"domain": "stage.up-example.com"
},
"production": {
"domain": "up-example.com"
Expand Down Expand Up @@ -303,7 +303,7 @@ $ up stack apply

After the changes have been applied, it can take roughly 10-40 minutes for CloudFront to distribute the configuration and SSL certificate globally, so until then our up-example.com domain won't work.

Once available https://up-example.com will always point to production via `up deploy production`, and https://dev.up-example.com/ will point to the latest deployment via `up`.
Once available https://up-example.com will always point to production via `up deploy production`, and https://stage.up-example.com/ will point to the latest deployment via `up`.

### Mapping Domains from External Registrars

Expand Down

0 comments on commit d273f38

Please sign in to comment.