diff --git a/CHANGELOG b/CHANGELOG
index a381c82..7aac018 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -1,3 +1,10 @@
+Version 0.8.2 (2019-12-07)
+==========================
+
+Bug fixes:
+- Enforce foreign key constraints in MySQL
+- Widen most text fields for MySQL
+
Version 0.8.1 (2019-10-28)
==========================
@@ -99,11 +106,11 @@ Bug fixes:
- Print command-line error messages more sensibly
- Allow exporting default configuration to standard output
- Fail correctly on authentication failure
-- Prefer JSON data over GET parameters in NextCloud News
+- Prefer JSON data over GET parameters in Nextcloud News
Changes:
- Simplify user management backend to minimize opportunity for bugs
-- Document previously unknown NextCloud News behaviour
+- Document previously unknown Nextcloud News behaviour
Version 0.4.0 (2018-10-26)
==========================
@@ -120,7 +127,7 @@ Bug fixes:
- Minor fixes to code and documentation
Changes:
-- Disable memory and time limits to avoid deadlocks with NextCloud News
+- Disable memory and time limits to avoid deadlocks with Nextcloud News
Version 0.3.0 (2018-01-12)
==========================
@@ -146,7 +153,7 @@ Bug fixes:
- Rename feeds correctly via TTRSS protocol
- Toggle marks correctly via TTRSS protocol
- Sort everything case-insensitively
-- Be even stricter about output data types in NextCloud News
+- Be even stricter about output data types in Nextcloud News
Changes:
- Do not omit read feeds from TTRSS' getCounters, to fix some clients
@@ -160,8 +167,8 @@ New features:
Bug fixes:
- Perform feed discovery *correctly*
-- Expose the incorrectDbCharset boolean in the NextCloud News server status
-- Give NextCloud News articles' guidHash attribute the correct type (string)
+- Expose the incorrectDbCharset boolean in the Nextcloud News server status
+- Give Nextcloud News articles' guidHash attribute the correct type (string)
Changes:
- Overhaul input type normalization to minimize bug opportunities
@@ -170,7 +177,7 @@ Version 0.1.1 (2017-09-30)
==========================
Bug fixes:
-- Perform feed discovery like NextCloud News does
+- Perform feed discovery like Nextcloud News does
- Respond correctly to HEAD requests
- Various minor fixes
diff --git a/UPGRADING b/UPGRADING
index c96f41c..a78867b 100644
--- a/UPGRADING
+++ b/UPGRADING
@@ -10,6 +10,14 @@ usually prudent:
- If installing from source, update dependencies with:
`composer install -o --no-dev`
+
+Upgrading from 0.8.1 to 0.8.2
+=============================
+
+- The database schema has changed from rev5 to rev6; if upgrading the database
+ manually, apply the 5.sql file
+
+
Upgrading from 0.7.1 to 0.8.0
=============================
@@ -22,6 +30,7 @@ Upgrading from 0.7.1 to 0.8.0
- zendframework/zend-diactoros (version 2.x)
- zendframework/zend-httphandlerrunner
+
Upgrading from 0.5.1 to 0.6.0
=============================
diff --git a/dist/apache.conf b/dist/apache.conf
index 575d3ae..3c27b5a 100644
--- a/dist/apache.conf
+++ b/dist/apache.conf
@@ -10,12 +10,12 @@
ProxyFCGISetEnvIf "true" SCRIPT_FILENAME "/usr/share/arsse/arsse.php"
ProxyPreserveHost On
- # NextCloud News v1.2, Tiny Tiny RSS API, TT-RSS newsfeed icons
+ # Nextcloud News v1.2, Tiny Tiny RSS API, TT-RSS newsfeed icons
ProxyPass "unix:/var/run/php/php7.2-fpm.sock|fcgi://localhost/usr/share/arsse"
- # NextCloud News API detection, Fever API
+ # Nextcloud News API detection, Fever API
# these locations should not be behind HTTP authentication
ProxyPass "unix:/var/run/php/php7.2-fpm.sock|fcgi://localhost/usr/share/arsse"
diff --git a/dist/nginx.conf b/dist/nginx.conf
index 1daabd4..6b488d7 100644
--- a/dist/nginx.conf
+++ b/dist/nginx.conf
@@ -23,7 +23,7 @@ server {
fastcgi_param REMOTE_USER $remote_user;
}
- # NextCloud News protocol
+ # Nextcloud News protocol
location /index.php/apps/news/api {
try_files $uri @arsse;
diff --git a/docs/en/010_About.md b/docs/en/010_About.md
index 3e6ec64..615185f 100644
--- a/docs/en/010_About.md
+++ b/docs/en/010_About.md
@@ -1,6 +1,6 @@
The Advanced RSS Environment (affectionately called "The Arsse") is a news aggregator server which implements multiple synchronization protocols. Unlike most other aggregator servers, The Arsse does not include a Web front-end (though one is planned as a separate project), and it relies on [existing protocols](Supported_Protocols) to maximize compatibility with [existing clients](Compatible_Clients). Supported protocols are:
-- NextCloud News
+- Nextcloud News
- Tiny Tiny RSS
- Fever
diff --git a/docs/en/020_Getting_Started/020_Download_and_Installation.md b/docs/en/020_Getting_Started/020_Download_and_Installation.md
index 8f0cadc..ed47a7d 100644
--- a/docs/en/020_Getting_Started/020_Download_and_Installation.md
+++ b/docs/en/020_Getting_Started/020_Download_and_Installation.md
@@ -2,7 +2,7 @@
# Downloading The Arse
-The latest version of The Arsse can be downloaded [from our releases page](https://code.mensbeam.com/MensBeam/arsse/releases). The attachments named _arsse-x.x.x.tar.gz_ should be used rather than those marked "Source Code".
+The latest version of The Arsse can be downloaded [from our Web site](https://thearsse.com/). If installing an older release from our archives, the attachments named _arsse-x.x.x.tar.gz_ should be used rather than those marked "Source Code".
Installation from source code is also possible, but the release packages are recommended.
diff --git a/docs/en/020_Getting_Started/030_Web_Server_Configuration.md b/docs/en/020_Getting_Started/030_Web_Server_Configuration.md
index 392f117..361624a 100644
--- a/docs/en/020_Getting_Started/030_Web_Server_Configuration.md
+++ b/docs/en/020_Getting_Started/030_Web_Server_Configuration.md
@@ -34,7 +34,7 @@ server {
fastcgi_param REMOTE_USER $remote_user;
}
- # NextCloud News protocol
+ # Nextcloud News protocol
location /index.php/apps/news/api {
try_files $uri @arsse;
@@ -92,12 +92,12 @@ Afterward the follow virtual host configuration should work, after modifying pat
ProxyFCGISetEnvIf "true" SCRIPT_FILENAME "/usr/share/arsse/arsse.php"
ProxyPreserveHost On
- # NextCloud News v1.2, Tiny Tiny RSS API, TT-RSS newsfeed icons
+ # Nextcloud News v1.2, Tiny Tiny RSS API, TT-RSS newsfeed icons
ProxyPass "unix:/var/run/php/php7.2-fpm.sock|fcgi://localhost/usr/share/arsse"
- # NextCloud News API detection, Fever API
+ # Nextcloud News API detection, Fever API
# these locations should not be behind HTTP authentication
ProxyPass "unix:/var/run/php/php7.2-fpm.sock|fcgi://localhost/usr/share/arsse"
diff --git a/docs/en/030_Supported_Protocols/010_NextCloud_News.md b/docs/en/030_Supported_Protocols/010_Nextcloud_News.md
similarity index 94%
rename from docs/en/030_Supported_Protocols/010_NextCloud_News.md
rename to docs/en/030_Supported_Protocols/010_Nextcloud_News.md
index a7dad69..a2c34d0 100644
--- a/docs/en/030_Supported_Protocols/010_NextCloud_News.md
+++ b/docs/en/030_Supported_Protocols/010_Nextcloud_News.md
@@ -13,7 +13,7 @@
-The NextCloud News protocol was the first supported by The Arsse, and has been supported in full since version 0.3.0.
+The Nextcloud News protocol was the first supported by The Arsse, and has been supported in full since version 0.3.0.
It allows organizing newsfeeds into single-level folders, and supports a wide range of operations on newsfeeds, folders, and articles.
@@ -25,7 +25,7 @@ It allows organizing newsfeeds into single-level folders, and supports a wide ra
- The feed updater ignores the `userId` parameter: feeds in The Arsse are deduplicated, and have no owner
- The `/feeds/all` route lists only feeds which should be checked for updates, and it also returns all `userId` attributes as empty strings: feeds in The Arsse are deduplicated, and have no owner
- The API's "updater" routes do not require administrator priviledges as The Arsse has no concept of user classes
-- The "updater" console commands mentioned in the protocol specification are not implemented, as The Arsse does not implement the required NextCloud subsystems
+- The "updater" console commands mentioned in the protocol specification are not implemented, as The Arsse does not implement the required Nextcloud subsystems
- The `lastLoginTimestamp` attribute of the user metadata is always the current time: The Arsse's implementation of the protocol is fully stateless
- Syntactically invalid JSON input will yield a `400 Bad Request` response instead of falling back to GET parameters
- Folder names consisting only of whitespace are rejected along with the empty string
@@ -36,4 +36,4 @@ It allows organizing newsfeeds into single-level folders, and supports a wide ra
# Interaction with nested folders
-Tiny Tiny RSS is unique in allowing newsfeeds to be grouped into folders nested to arbitrary depth. When newsfeeds are placed into nested folders, they simply appear in the top-level folder when accessed via the NextCloud News protocol.
+Tiny Tiny RSS is unique in allowing newsfeeds to be grouped into folders nested to arbitrary depth. When newsfeeds are placed into nested folders, they simply appear in the top-level folder when accessed via the Nextcloud News protocol.
diff --git a/docs/en/030_Supported_Protocols/020_Tiny_Tiny_RSS.md b/docs/en/030_Supported_Protocols/020_Tiny_Tiny_RSS.md
index 1dc4ba0..e34ca45 100644
--- a/docs/en/030_Supported_Protocols/020_Tiny_Tiny_RSS.md
+++ b/docs/en/030_Supported_Protocols/020_Tiny_Tiny_RSS.md
@@ -59,7 +59,7 @@ The Arsse does not currently support the entire protocol. Notably missing featur
# Interaction with HTTP authentication
-Tiny Tiny RSS itself is unaware of HTTP authentication: if HTTP authentication is used in the server configuration, it has no effect on authentication in the API. The Arsse, however, makes use of HTTP authentication for NextCloud News, and can do so for TT-RSS as well. In a default configuration The Arsse functions in the same way as TT-RSS: HTTP authentication and API authentication are completely separate and independent. Alternative behaviour is summarized below:
+Tiny Tiny RSS itself is unaware of HTTP authentication: if HTTP authentication is used in the server configuration, it has no effect on authentication in the API. The Arsse, however, makes use of HTTP authentication for Nextcloud News, and can do so for TT-RSS as well. In a default configuration The Arsse functions in the same way as TT-RSS: HTTP authentication and API authentication are completely separate and independent. Alternative behaviour is summarized below:
- With default settings:
- Clients may optionally provide HTTP credentials
diff --git a/docs/en/030_Supported_Protocols/index.md b/docs/en/030_Supported_Protocols/index.md
index 6124960..7e58df6 100644
--- a/docs/en/030_Supported_Protocols/index.md
+++ b/docs/en/030_Supported_Protocols/index.md
@@ -1,6 +1,6 @@
The Arsse was designed from the start as a server for multiple synchronization protocols which clients can make use of. Currently the following protocols are supported:
-- [NextCloud News](NextCloud_News)
+- [Nextcloud News](Nextcloud_News)
- [Tiny Tiny RSS](Tiny_Tiny_RSS)
- [Fever](Fever)
diff --git a/docs/en/040_Compatible_Clients.md b/docs/en/040_Compatible_Clients.md
index a293c7b..279c25f 100644
--- a/docs/en/040_Compatible_Clients.md
+++ b/docs/en/040_Compatible_Clients.md
@@ -127,13 +127,13 @@ The Arsse does not at this time have any first party clients. However, because T