@ -444,6 +444,9 @@ Chrome and Firefox will still complain your certificate has not been verified by
Now you have a valid, trusted certificate for development.
Now you have a valid, trusted certificate for development.
#### Built-in certificate
As a quick win, you can run `ws` with the `https` flag. This will launch an HTTPS server using a [built-in certificate](https://github.com/75lb/local-web-server/tree/master/ssl) registered to the domain 127.0.0.1.
### Stored config
### Stored config
Use the same options every time? Persist then to `package.json`:
Use the same options every time? Persist then to `package.json`:
@ -582,8 +585,8 @@ serving at http://localhost:8100
- [.forbid] <code>Array.<string></code> - A list of forbidden routes, each route being an [express route-path](http://expressjs.com/guide/routing.html#route-paths).
- [.spa] <code>string</code> - specify an SPA file to catch requests for everything but static assets.
- [.forbid] <code>Array.<string></code> - A list of forbidden routes, each route being an [express route-path](http://expressjs.com/guide/routing.html#route-paths).
- [.spa] <code>string</code> - specify an SPA file to catch requests for everything but static assets.
@ -444,6 +444,9 @@ Chrome and Firefox will still complain your certificate has not been verified by
Now you have a valid, trusted certificate for development.
Now you have a valid, trusted certificate for development.
#### Built-in certificate
As a quick win, you can run `ws` with the `https` flag. This will launch an HTTPS server using a [built-in certificate](https://github.com/75lb/local-web-server/tree/master/ssl) registered to the domain 127.0.0.1.
### Stored config
### Stored config
Use the same options every time? Persist then to `package.json`:
Use the same options every time? Persist then to `package.json`:
@ -589,4 +592,4 @@ serving at http://localhost:8100