Skip to content

Commit

Permalink
[README] Update the instructions to include step about npm run prod
Browse files Browse the repository at this point in the history
… first

Probably we eventually want to make `npm run dev` work correctly without
requiring `npm run prod` first, but this seems like an OK stopgap until then.
  • Loading branch information
ccheever committed Mar 15, 2020
1 parent cf6d76f commit f00f4f5
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

Clone this sucker, run `npm install`, and you’re in business.

`npm run dev` will build your static assets and spin up a local instance of the site. That usually runs at [https://localhost:8080](https://localhost:8080), unless you already have asomething running on that port—it’ll give you a URL in your terminal.
Before you start developing, you may need to run `npm run prod` one time and then `Ctrl+C` to kill it once the output stops. This will generate some static assets that the project needs. You probably only need to do this once when you first clone the repo.

`npm run dev` will spin up a local instance of the site. That usually runs at [https://localhost:8080](https://localhost:8080), unless you already have asomething running on that port—it’ll give you a URL in your terminal.

When you push a change, the CI will get kicked off at https://app.netlify.com/sites/upbeat-lovelace-3e9fff/deploys

0 comments on commit f00f4f5

Please sign in to comment.