@@ -167,7 +167,7 @@ $ solid start --help
167167
168168 --root [value] Root folder to serve (default: './data')
169169 --port [value] SSL port to use
170- --serverUri [value] Solid server uri (default: 'https://localhost:8443')
170+ --server-uri [value] Solid server uri (default: 'https://localhost:8443')
171171 --webid Enable WebID authentication and access control (uses HTTPS)
172172 --mount [value] Serve on a specific URL path (default: '/')
173173 --config-path [value]
@@ -182,7 +182,7 @@ $ solid start --help
182182 --idp [value] Obsolete; use --multiuser
183183 --no-live Disable live support through WebSockets
184184 --proxy [value] Obsolete; use --corsProxy
185- --corsProxy [value] Serve the CORS proxy on this path
185+ --cors-proxy [value] Serve the CORS proxy on this path
186186 --suppress-data-browser Suppress provision of a data browser
187187 --data-browser-path [value] An HTML file which is sent to allow users to browse the data (eg using mashlib.js)
188188 --suffix-acl [value] Suffix for acl files (default: '.acl')
@@ -191,18 +191,21 @@ $ solid start --help
191191 --error-pages [value] Folder from which to look for custom error pages files (files must be named <error-code>.html -- eg. 500.html)
192192 --force-user [value] Force a WebID to always be logged in (useful when offline)
193193 --strict-origin Enforce same origin policy in the ACL
194- --useEmail Do you want to set up an email service?
194+ --use-email Do you want to set up an email service?
195195 --email-host [value] Host of your email service
196196 --email-port [value] Port of your email service
197197 --email-auth-user [value] User of your email service
198198 --email-auth-pass [value] Password of your email service
199- --useApiApps Do you want to load your default apps on /api/apps?
199+ --use-api-apps Do you want to load your default apps on /api/apps?
200200 --api-apps [value] Path to the folder to mount on /api/apps
201201 --redirect-http-from [value] HTTP port or ','-separated ports to redirect to the solid server port (e.g. "80,8080").
202202 --server-name [value] A name for your server (not required, but will be presented on your server's frontpage)
203203 --server-description [value] A description of your server (not required)
204204 --server-logo [value] A logo that represents you, your brand, or your server (not required)
205- -v, --verbose Print the logs to console
205+ --enforce-toc Do you want to enforce Terms & Conditions for your service?
206+ --toc-uri [value] URI to your Terms & Conditions
207+ --support-email [value] The support email you provide for your users (not required)
208+ -q, --quiet Do not print the logs to console
206209 -h, --help output usage information
207210 ```
208211
@@ -226,8 +229,8 @@ docker run -p 8443:8443 --name solid node-solid-server
226229```
227230
228231This will enable you to login to solid on https://localhost:8443 and then create a new account
229- but not yet use that account. After a new account is made you will need to create an entry for
230- it in your local (/etc/)hosts file in line with the account and subdomain i.e.
232+ but not yet use that account. After a new account is made you will need to create an entry for
233+ it in your local (/etc/)hosts file in line with the account and subdomain i.e.
231234
232235127.0.0.1 newsoliduser.localhost
233236
@@ -391,14 +394,13 @@ blacklist profanities by default.
391394
392395## Quota
393396
394- By default, a file ` serverSide.ttl ` will be installed to new PODs. Its
395- current function is to set a quota for disk usage of just 25 MB, which
396- is what we can be sure the current prototype can tolerate under
397- load. This file is not writeable to users, but as server administrator
398- you can remove it if you don't want to impose a quota. It is currently
399- adviceable to remove it rather than set a large quota, because the
400- current implementation will impair write performance if there is a lot
401- of data.
397+ By default, a file ` serverSide.ttl.inactive ` will be installed to new
398+ PODs. If you rename it to ` serverSide.ttl ` , it will currently set a
399+ quota for disk usage. This file is not writeable to users, only
400+ server administrators who are authorized on the backend can modify
401+ it. It is currently adviceable to remove it or set it inactive rather
402+ than set a large quota, because the current implementation will impair
403+ write performance if there is a lot of data.
402404
403405## Contribute to Solid
404406
0 commit comments