|
1 | 1 | # History |
2 | 2 |
|
| 3 | +## 5.0.0 |
| 4 | + |
| 5 | +- Node versions greater than 8 are supported. |
| 6 | +- Changes to vocabulary use: |
| 7 | + - `solid:inbox` is deprecated in favour of `ldp:inbox`. |
| 8 | + - `acl:defaultForNew` is deprecated in favour of `acl:default`. |
| 9 | +- Terms of Service may be added and enforced for new registrations, |
| 10 | + but is disabled by default. |
| 11 | +- DELETE operations on a resource now require that the user has write permissions on |
| 12 | + the file's container |
| 13 | +- Improved support for logout ensures users can use different |
| 14 | + identities. |
| 15 | +- The profile container is now public readable by default. |
| 16 | +- Access Control: |
| 17 | + - The Access Control List system has undergone extensive |
| 18 | + changes. Security has been tightened, and some unsafe practices that |
| 19 | + where web apps was authorized access in the past are now not |
| 20 | + permitted. |
| 21 | + - The browser-reported `Origin` header will now be checked by |
| 22 | + default, and the ACL system can be used to restrict access |
| 23 | + to applications for added security. |
| 24 | + - Users can add `trustedApp` entries to their profile using a new databrowser pane. |
| 25 | + You will see an 'A' icon added while you view a Person's profile URL |
| 26 | + with the data browser (might have to hit refresh in your browser and make sure you |
| 27 | + are viewing a WebId URL like https://localhost:8443/profile/card#me). |
| 28 | +- Logging is now verbose by default so the `-v` option has been |
| 29 | + removed and a `--quiet` option has been added to mute the log. |
| 30 | +- To be bug compliant with 4.x releases, if a rule for public readable |
| 31 | + root / does not exist, it will check in /index.html.acl (see issue #1063) |
| 32 | +- Command line options are now kebab-cased rather than camelCased, |
| 33 | + config options may be both. |
| 34 | +- Resource with no extension now have '$.ttl' appended in the filename (see upgrades notes below). |
| 35 | +- Many smaller fixes. |
| 36 | + |
| 37 | +#### 5.0.0 Upgrade Notes |
| 38 | + |
| 39 | +- As of v5.0.0, all Turtle files need an extension. (**Intervention needed when updating from < 5.0.0!**) |
| 40 | + - **How to upgrade?** |
| 41 | + 1. Stop the server. |
| 42 | + 2. Update node-solid-server to 5.0.0. |
| 43 | + 3. Make a backup of your `data/` and `config/` folders. |
| 44 | + 4. Invoke `solid migrate-legacy-resources -v`. |
| 45 | + This makes the files in your `data/` and `config/` folders |
| 46 | + automatically compatible with the new system. |
| 47 | + You only need to do this once. |
| 48 | + Different data folders can be migrated as well with the `-p` option: |
| 49 | + `solid migrate-legacy-resources -p my/custom/data/folder -v` |
| 50 | + 5. You can now start the server again as usual. |
| 51 | + - **Why?** |
| 52 | + Before version 5.0.0, `https://pod.example/profile/card` |
| 53 | + would map to `file:///solid/profile/card`, with the _assumption_ |
| 54 | + that it uses content-type `text/turtle`. |
| 55 | + Now, this URL will map to `file:///solid/profile/card$.ttl` instead, |
| 56 | + which makes the content-type automatically detectable. |
| 57 | + This fixes many of the old Content-Type-related bugs. |
| 58 | + _More information: https://www.w3.org/DesignIssues/HTTPFilenameMapping.html_ |
| 59 | + |
| 60 | +## 4.4.0 |
| 61 | + |
| 62 | +- Introduce a quota system. Delete the /settings/serverSide.ttl in the |
| 63 | + user's POD to disable, or edit to fit your resource constraints. |
| 64 | + |
| 65 | +#### Changelog is incomplete for much of the 4.x series |
| 66 | + |
3 | 67 | ## 4.1.0 |
4 | 68 |
|
5 | 69 | - Add support for Group Access Control Lists. |
|
0 commit comments