How to Install Tiny Tiny RSS on AlmaLinux 9 or Rocky Linux 9 with Docker
The original Tiny Tiny RSS was retired in November 2025. Install the maintained fork with Docker, PostgreSQL and an Nginx HTTPS proxy on AlmaLinux 9 or Rocky Linux 9.
This guide sets up Tiny Tiny RSS (tt-rss), the self-hosted web feed reader, on AlmaLinux 9, Rocky Linux 9 or CentOS Stream 9. At the end you will have tt-rss running in Docker containers with PostgreSQL, published at https://rss.example.com/tt-rss/ through Nginx with a Let's Encrypt certificate, and a background updater that keeps your feeds fresh.
Project status: read this first
The original Tiny Tiny RSS project was retired by its author on 1 November 2025, and its former Git hosting and forum were shut down. Development continues in a fork created from the code as of 3 October 2025 by a long-time contributor. The maintained code base today is the tt-rss/tt-rss repository on GitHub, and tt-rss.org carries its documentation. The maintainers state that no major breaking changes are planned and that the main branch is meant to be stable; there are no numbered releases, you simply run the latest image.
Three practical consequences:
- Docker is the main and recommended way to run tt-rss. The project's installation guide does not document a classic "unpack into the web root" installation any more, and the manual LAMP-style setup that older tutorials describe for CentOS 7 (itself end-of-life since June 2024) should not be used.
- Podman is explicitly not supported. On RHEL-compatible systems, where Podman is the default container tool, install Docker Engine instead.
- Image names changed. The current images are
supahgreg/tt-rssandsupahgreg/tt-rss-web-nginxon Docker Hub, andghcr.io/tt-rss/tt-rssandghcr.io/tt-rss/tt-rss-web-nginxon the GitHub Container Registry, built forlinux/amd64andlinux/arm64.
Requirements
- A server running AlmaLinux 9, Rocky Linux 9 or CentOS Stream 9 and a user with
sudorights (deployin the examples). - Docker Engine with the Compose plugin.
- A DNS record such as
rss.example.compointing to the server.
Step 1: Install Docker Engine
Add Docker's repository and install the engine and the Compose plugin. Docker documents this repository for CentOS Stream 9; AlmaLinux 9 and Rocky Linux 9 are RHEL-compatible and use the same packages, although Docker does not list them as tested platforms.
sudo dnf -y install dnf-plugins-core
sudo dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo dnf install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo systemctl enable --now docker
Add your user to the docker group, then log out and back in:
sudo usermod -aG docker deploy
Step 2: Create the configuration
Create a directory for the installation. The compose file mounts a config.d sub-directory into the containers, so create that as well (it can stay empty):
mkdir -p ~/ttrss/config.d
cd ~/ttrss
Create ~/ttrss/.env. Replace both passwords; do not put quotes around values.
# Password of the built-in "admin" user, applied on every start.
ADMIN_USER_PASS=choose-an-admin-password
# Database credentials used by the db and app containers.
TTRSS_DB_USER=postgres
TTRSS_DB_NAME=postgres
TTRSS_DB_PASS=choose-a-database-password
# Public address of the installation.
TTRSS_SELF_URL_PATH=https://rss.example.com/tt-rss
# Listen on the loopback address only; Nginx on the host is the public entry point.
HTTP_PORT=127.0.0.1:8280
If you leave out ADMIN_USER_PASS, a random password is generated at start-up and written to the log of the app container. Any other tt-rss option can be set here with a TTRSS_ prefix.
Create ~/ttrss/docker-compose.yml with the services from the project's installation guide:
services:
db:
image: postgres:17-alpine
restart: unless-stopped
env_file:
- .env
environment:
- POSTGRES_USER=${TTRSS_DB_USER}
- POSTGRES_PASSWORD=${TTRSS_DB_PASS}
- POSTGRES_DB=${TTRSS_DB_NAME}
volumes:
- db:/var/lib/postgresql/data
app:
image: supahgreg/tt-rss:latest
restart: unless-stopped
env_file:
- .env
volumes:
- app:/var/www/html
- ./config.d:/opt/tt-rss/config.d:ro
depends_on:
- db
updater:
image: supahgreg/tt-rss:latest
restart: unless-stopped
env_file:
- .env
volumes:
- app:/var/www/html
- ./config.d:/opt/tt-rss/config.d:ro
depends_on:
- app
command: /opt/tt-rss/updater.sh
web-nginx:
image: supahgreg/tt-rss-web-nginx:latest
restart: unless-stopped
env_file:
- .env
ports:
- ${HTTP_PORT}:80
volumes:
- app:/var/www/html:ro
depends_on:
- app
volumes:
db:
app:
The app container runs PHP-FPM, updater fetches feeds in the background, and web-nginx serves the application on the port set in HTTP_PORT. To pull from the GitHub Container Registry instead of Docker Hub, replace the two image names with ghcr.io/tt-rss/tt-rss:latest and ghcr.io/tt-rss/tt-rss-web-nginx:latest. Keep the PostgreSQL 17 image unless you have a reason to change it: version 18 images use a different data path and need the volume mounted at /var/lib/postgresql.
Step 3: Start tt-rss
cd ~/ttrss
docker compose up -d
docker compose ps
The first start creates the database schema. Follow the log of the application container until it settles:
docker compose logs -f app
A quick local test confirms that the web container answers:
curl -I http://127.0.0.1:8280/tt-rss/
Step 4: Publish it through Nginx with HTTPS
Install Nginx on the host and allow it to connect to the local container port, which SELinux blocks by default:
sudo dnf install nginx
sudo setsebool -P httpd_can_network_connect 1
sudo systemctl enable --now nginx
Create /etc/nginx/conf.d/ttrss.conf. The X-Forwarded-Proto header matters: without it tt-rss generates plain http:// links behind an HTTPS proxy.
server {
listen 80;
server_name rss.example.com;
location = / {
return 302 /tt-rss/;
}
location /tt-rss/ {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://127.0.0.1:8280/tt-rss/;
}
}
Reload Nginx, open the firewall and request the certificate with Certbot from EPEL, which adds the TLS settings to this server block:
sudo nginx -t
sudo systemctl reload nginx
sudo firewall-cmd --permanent --add-service=http --add-service=https
sudo firewall-cmd --reload
sudo dnf install epel-release
sudo dnf install certbot python3-certbot-nginx
sudo certbot --nginx -d rss.example.com
Step 5: Log in and verify
Open https://rss.example.com/tt-rss/ and log in as admin with the password from ADMIN_USER_PASS. Subscribe to a feed, then check that the updater is working:
cd ~/ttrss
docker compose logs --tail=30 updater
For daily reading, create a normal user under Preferences and keep admin for administration. You can also let the containers create that user by setting AUTO_CREATE_USER and AUTO_CREATE_USER_PASS in .env and running docker compose up -d again.
Updates and backups
Because the project is rolling, updating means pulling the current images and recreating the containers. If the database schema changed, tt-rss shows an upgrade screen on the next login.
cd ~/ttrss
docker compose pull && docker compose up -d
Everything worth keeping is in the PostgreSQL database. Dump it from the host and store the file elsewhere:
cd ~/ttrss
source .env
docker compose exec \
-e PGPASSWORD="$TTRSS_DB_PASS" \
db \
/bin/bash \
-c "export PGPASSWORD=$TTRSS_DB_PASS \
&& pg_dump -U $TTRSS_DB_USER $TTRSS_DB_NAME" \
| gzip -9 > backup.sql.gz
The installation guide also describes an optional backups container that writes weekly dumps to its own volume, and you can export your subscriptions as OPML under Preferences, Feeds, OPML as an additional, incomplete safety net.
Frequently asked questions
Is Tiny Tiny RSS discontinued?
The original project is: it was retired on 1 November 2025. The software itself is still developed in the tt-rss/tt-rss fork on GitHub, which publishes current container images. It is a small volunteer-run project, so judge for yourself whether that is enough for your use, and keep regular database dumps and an OPML export so that you can move to another reader if needed.
I run the old container images. How do I switch?
The maintainers describe the new images as drop-in replacements. Back up the database, change the image: lines in your docker-compose.yml to the names listed above, then run docker compose pull && docker compose up -d.
Can tt-rss answer at the root of the domain instead of /tt-rss/?
Yes. Add APP_WEB_ROOT=/var/www/html/tt-rss and an empty APP_BASE= to .env, remove /tt-rss from TTRSS_SELF_URL_PATH, and proxy location / to http://127.0.0.1:8280/ in Nginx. The details are in the tt-rss installation guide.
Can I install it without Docker, directly under Apache or Nginx with PHP?
The current documentation only covers the container setup. The project states that its minimum PHP version follows the PHP in Debian's current stable release, which is newer than the default PHP on a RHEL 9 compatible system, so a host installation there would be an unsupported do-it-yourself effort.