Skip to content
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.

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

update cli version to 0.8 in docs #633

Merged
merged 3 commits into from
Jun 20, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/complex-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ fi

npm run deploy

npm install -g @lhci/cli@0.7.x
npm install -g @lhci/cli@0.8.x
lhci healthcheck --fatal
lhci collect --url=http://localhost:9000/index.html
lhci assert --preset="lighthouse:recommended"
Expand Down Expand Up @@ -121,7 +121,7 @@ Now that we have our environment ready, time to run Lighthouse CI. The `collect`

# Install Lighthouse CI
# If you're already using node to manage your project, add it to your package.json `devDependencies` instead to skip this step.
npm install -g @lhci/cli@0.7.x
npm install -g @lhci/cli@0.8.x

# Run a healthcheck to make sure everything looks good before we run collection.
lhci healthcheck --fatal
Expand Down
16 changes: 8 additions & 8 deletions docs/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ jobs:
npm run build
- name: run Lighthouse CI
run: |
npm install -g @lhci/cli@0.7.x
npm install -g @lhci/cli@0.8.x
lhci autorun
```

Expand All @@ -113,7 +113,7 @@ node_js: v12
addons:
chrome: stable
before_install:
- npm install -g @lhci/cli@0.7.x
- npm install -g @lhci/cli@0.8.x
script:
- npm run build
- lhci autorun
Expand All @@ -138,7 +138,7 @@ jobs:
- checkout
- run: npm install
- run: npm run build
- run: sudo npm install -g @lhci/cli@0.7.x
- run: sudo npm install -g @lhci/cli@0.8.x
- run: lhci autorun
```

Expand Down Expand Up @@ -173,7 +173,7 @@ lhci:
script:
- npm install
- npm run build
- npm install -g @lhci/cli@0.7.x
- npm install -g @lhci/cli@0.8.x
- lhci autorun --upload.target=temporary-public-storage --collect.settings.chromeFlags="--no-sandbox" || echo "LHCI failed!"
```

Expand Down Expand Up @@ -215,7 +215,7 @@ npm run build
export CHROME_PATH=$(which google-chrome-stable)
export LHCI_BUILD_CONTEXT__EXTERNAL_BUILD_URL="$BUILD_URL"

npm install -g @lhci/cli@0.7.x
npm install -g @lhci/cli@0.8.x
lhci autorun
```

Expand Down Expand Up @@ -264,7 +264,7 @@ steps:
waitFor: ['build']
name: cypress/browsers:node14.15.0-chrome86-ff82
entrypoint: '/bin/sh'
args: ['-c', 'npm install -g @lhci/cli@0.7.x && lhci autorun --failOnUploadFailure']
args: ['-c', 'npm install -g @lhci/cli@0.8.x && lhci autorun --failOnUploadFailure']
env:
- 'LHCI_BUILD_CONTEXT__CURRENT_BRANCH=$BRANCH_NAME'

Expand Down Expand Up @@ -370,7 +370,7 @@ jobs:
npm run build
- name: run Lighthouse CI
run: |
npm install -g @lhci/cli@0.7.x
npm install -g @lhci/cli@0.8.x
lhci autorun
env:
LHCI_GITHUB_APP_TOKEN: ${{ secrets.LHCI_GITHUB_APP_TOKEN }}
Expand Down Expand Up @@ -468,7 +468,7 @@ Once the server is set up, _on your local laptop or desktop_, make sure you can
```bash
$ curl https://your-lhci-server.example.com/version # Make sure you can connect to your server.
0.x.x
$ npm install -g @lhci/cli@0.7.x # Install the Lighthouse CI CLI.
$ npm install -g @lhci/cli@0.8.x # Install the Lighthouse CI CLI.
Installing...
$ lhci wizard # Use the wizard to create a project.
? Which wizard do you want to run? new-project
Expand Down
4 changes: 0 additions & 4 deletions docs/server.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,3 @@ const lhci = require('@lhci/server');
### Firewall Rules

You can also protect your server through firewall rules to prevent it from being accessed from outside your internal network. Refer to your infrastructure provider's documentation on how to setup firewall rules to block external IP addresses from accessing the server. Don't forget to allow your CI machines!

```

```