@@ -77,6 +77,10 @@ $ openssl genrsa 2048 > ../localhost.key
7777$ openssl req -new -x509 -nodes -sha256 -days 3650 -key ../localhost.key -subj '/CN=*.localhost' > ../localhost.cert
7878```
7979
80+ Note that this example creates the ` localhost.cert ` and ` localhost.key ` files
81+ in a directory one level higher from the current, so that you don't
82+ accidentally commit your certificates to ` solid ` while you're developing.
83+
8084### Run multi-user server (intermediate)
8185
8286You can run ` solid ` so that new users can sign up, in other words, get their WebIDs _ username.yourdomain.com_ .
@@ -317,20 +321,8 @@ without them.
317321When deploying ` solid ` in production, we recommend that you go the
318322usual Certificate Authority route to generate your SSL certificate (as you
319323would with any website that supports HTTPS). However, for testing it locally,
320- you can easily generate a self-signed certificate for whatever domain you're
321- working with.
322-
323- For example, here is how to generate a self-signed certificate for ` localhost `
324- using the ` openssl ` library:
325-
326- ``` bash
327-
328- solid --webid --port 8443 --cert ../localhost.cert --key ../localhost.key -v
329- ```
330-
331- Note that this example creates the ` localhost.cert ` and ` localhost.key ` files
332- in a directory one level higher from the current, so that you don't
333- accidentally commit your certificates to ` solid ` while you're developing.
324+ you can easily [ generate a self-signed certificate for whatever domain you're
325+ Working with] ( https://github.com/solid/node-solid-server#how-do-i-get-an-ssl-key-and-certificate ) .
334326
335327#### Accessing your server
336328
0 commit comments