You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
+
80
84
### Run multi-user server (intermediate)
81
85
82
86
You can run `solid` so that new users can sign up, in other words, get their WebIDs _username.yourdomain.com_.
@@ -105,7 +109,7 @@ Your users will have a dedicated folder under `./accounts`. Also, your root doma
105
109
### Running Solid behind a reverse proxy (such as NGINX)
106
110
See [Running Solid behind a reverse proxy](https://github.com/solid/node-solid-server/wiki/Running-Solid-behind-a-reverse-proxy).
107
111
108
-
##### How can send emails to my users with my Gmail?
112
+
##### How can I send emails to my users with my Gmail?
109
113
110
114
> To use Gmail you may need to configure ["Allow Less Secure Apps"](https://www.google.com/settings/security/lesssecureapps) in your Gmail account unless you are using 2FA in which case you would have to create an [Application Specific](https://security.google.com/settings/security/apppasswords) password. You also may need to unlock your account with ["Allow access to your Google account"](https://accounts.google.com/DisplayUnlockCaptcha) to use SMTP.
111
115
@@ -317,20 +321,8 @@ without them.
317
321
When deploying `solid` in production, we recommend that you go the
318
322
usual Certificate Authority route to generate your SSL certificate (as you
319
323
would 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`
0 commit comments