b08c4ef243
Apply sentence case to all H1s in docs/en/ and remove redundant "FreshRSS" from titles where the docs site context already implies it. Align the three section index titles to "Administrator/Developer/User manual", matching the existing root H1 "FreshRSS manual (English)". Add missing H1s to two pages that were silently dropped from the sidebar: the user FAQ and the Caddy reverse proxy page. The sidebar template uses page.title (derived from H1 by jekyll-titles-from-headings), so pages without an H1 had title=nil and were skipped. Update sidebar parent labels in docs_nav.html and the chapter list in en/index.md to use the new "* manual" naming. Update link text in section indexes that referenced the old H1s. Bundle two grammar fixes encountered along the way: "an User Interface" -> "a user interface", and drop the awkward "the" in "Configuring the email address validation". EN only. No filenames, URLs, or anchor targets changed (anchors come from H2 and below, which are untouched). FR is generated from EN via po4a and will be regenerated separately. Co-authored-by: Bjørn A. Andersen <polybjorn@users.noreply.github.com>
2.6 KiB
Server requirements
FreshRSS is a web application. This means you’ll need a web server to run it. FreshRSS requirements are really low, so it should run on most shared host servers, or any old computer you happen to have on hand.
You need to verify that your server can run FreshRSS before installing it. If your server has the proper requirements and FreshRSS does not work, please contact us to find a solution.
| Software | Recommended | Also Works With |
|---|---|---|
| Web server | Apache 2.4 | nginx, lighttpd |
| PHP | PHP 8.1+ | FreshRSS 1.24.3: PHP 7.4+ FreshRSS 1.22.1: PHP 7.2+ |
| PHP modules | Required: libxml, cURL, JSON, PDO_MySQL, PCRE and ctype. Required (32-bit only): GMP Recommended: Zlib, mbstring, iconv, ZipArchive For the whole modules list see Dockerfile |
|
| Database | PostgreSQL 10+ | SQLite, MariaDB 10.6+, MySQL 8.0+ |
| Browser | Firefox | Chrome, Opera, Safari, or Edge |
Getting the appropriate version of FreshRSS
FreshRSS has two different releases. It is better if you spend some time to understand the purpose of each release.
Stable release
This version is really stable, tested thoroughly, and you should not face any major bugs.
Stable releases are not released on a set schedule. Rather, they are released whenever we consider that our goal for new features is reached, and the software is stable.
It could happen that we make two releases in a short span of time if we have a really good coding pace. In reality, we are all working on the project in our spare time, so a new release usually occurs every few months.
Development version
As its name suggests, the development version is the working codebase, intended for developers. This release may be unstable!
If you want to keep track of the most recent enhancements or help the developers with bug reports, this is the branch for you. If you use this version, please keep in mind that you need to follow the branch activity on GitHub (via the branch RSS feed, for instance), and manually pull new commits.
Some say that the main developers use this branch on a daily basis without problem. They may know what they are doing…