Tiny Tiny RSS

(2021) Build your own RSS reader Tiny Tiny RSS tutorial, docker installation Awesome TTRSS

Tiny Tiny RSS is a PHP-based free open source RSS aggregation reader, is currently building their own RSS feeds to choose more of a way, daddy build notes previously shared is the way to install Tiny Tiny RSS through the source code, recently found that the official only support docker installation TTRSS, soThis tutorial is updated in 2021How to install Awesome TTRSS using docker one at a time.

Awesome TTRSS is designed to provide a "One-stop Containerization" s Tiny Tiny RSS solution to enhance the user experience by providing an easy deployment method and some additional plugins. (The official Tiny Tiny RSS milquetoast didn't work out how to install it, ( ╯□╰ ))

Preparation before building your own Tiny Tiny RSS

To build the Tiny Tiny RSS service ourselves, we need to prepare the following.

  1. a VPS server, if you want to subscribe to a foreign source, it is recommended to choose a foreign VPS.
  2. A domain name, or not, if you use the server IP to access it directly.

Server can choose domestic or foreign, if you many foreign website subscription source, then recommend foreign server, so that the network is smooth a little.

If you have a domain name, you can register a domain name for a year for a few dollars to a few dozen dollars, or you can just use a second-level domain name if you already have one. See alsoDomain Name Guide.

Steps to build your own Tiny Tiny RSS

Create a VPS server

The server piece is recommended to choose aForeign VPS, milkman here to choose theVultrYou can buy a server for as little as $2.50 a month, but we recommend starting at $5 for better performance and the ability to build websites.

Vultr Server Purchase Tutorial

Operating system here choose the CentOS 7 version, the configuration is recommended to choose at least $ 5, the performance will be better, and also by the way on top of this serverBuild a website.

Installation of pagoda panels

After the server is created, we install the pagoda panel to the server.

Pagoda Panel is a server operation and maintenance panel that can help us visualize many operations that require inputting Linux command line, a gospel for whites.

The installation of the pagoda panel daddy builder notes previously posted a special tutorial, please refer to.

2021 Pagoda panel installation tutorial (updated installation video tutorial)

Installing docker and docker-compose

Once the pagoda panel is installed, select the software store on the left side, then search for docker to install.

If you want to install docker manually using a terminal, the command is as follows.

curl -sSL https://get.docker.com/ | sh
systemctl enable --now docker

Once the Docker manager is installed, we also need to install docker-compose manually.

You can install docker-compose using the terminal in the pagoda panel, or by entering the following command inside xShell (the latest version at the time of this tutorial is 1.29.2).

curl -L https://github.com/docker/compose/releases/download/1.29.2/docker-compose- `uname -s`-`uname -m` -o /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

After the installation is complete, enter the following command to see if the installation was successful.

docker -v
docker-compose -v

Install Awesome TTRSS

Awesome TTRSS can be installed by both docker and docker-compose, here we use the docker-compose method.

1、Downloaddocker-compose.ymlThis file goes to a random folder on the server.

Open the pagoda panel, the files on the left side, then by default it will jump to /www/wwwroot under which the tutorial is saved to.

Click Remote Download and enter https://raw.githubusercontent.com/HenryQW/Awesome-TTRSS/main/docker-compose.yml for the URL address, then OK.

Next, click Edit this docker-compose.yml file in the file manager of the pagoda panel and change the following 3 parameters.

SELF_URL_PATH=http://localhost:181/ # Change localhost to the IP of your own server, so that you can access it later by IP to see if it is working properly.
DB_PASS=ttrss # Change ttrss to the same value as the following parameter.
POSTGRES_PASSWORD=ttrss # Change ttrss to the same value as above, that is, use the same password for both parameters.

When you have finished making changes, save the file and click Terminal.

Type docker-compose up -d, then when prompted with done, the service deployment starts successfully.

Modify Tiny Tiny RSS configuration

After starting TTRSS with the above command, we open the IP of your VPS plus port 181 access through a browser and the Tiny Tiny RSS login screen will appear.

If you find that you can't open TTRSS by typing VPSIP:181, first check if the firewall is not open on port 181.

Pagoda panel app store search firewall, then go to the firewall inside to add a tcp rule for port 181 on it.

Enter the default user nameadminand passwordpasswordLog in.

In the top right corner of the screen, click on the three bars and select Preferences to enter the settings.

Select Simplified Chinese in the Language item and then save it, it will become Simplified Chinese interface.

The rest of the settings can be done by yourself according to the actual situation.

Binding Domains for Tiny Tiny RSS

Accessing Tiny Tiny RSS via IP+port is not very convenient after all, so let's bind a domain name to Tiny Tiny RSS.

Add a website at the website in the pagoda panel, no need to create FTP and database, just fill in the domain name and OK it.

Next, click the Settings button behind the website and select Reverse Proxy on the left side of the settings screen.

The proxy name is filled in randomly, the target url is filled in http://127.0.0.1:181 and submitted.

Then go back to the file manager, edit the docker-compose.yml file, change the URL after SELF_URL_PATH= to the URL of your bound domain, and save it.

Open a terminal and type docker-compose up -d to deploy again.

Then you can open Tiny Tiny RSS by accessing it through the domain name.

Thanks

Here, the installation tutorial of Tiny Tiny RSS is shared, thanks toimhuandBig Bird BlogThe tutorial was shared by the daddy, who also learned to figure out this tutorial by searching to their articles.

Also, thanks toAwesome TTRSSThe project author's dedication has brought us a better user experience with the Tiny Tiny RSS reader project.

5/5 - (5 votes)

17 thoughts on “(2021)自建RSS阅读器Tiny Tiny RSS教程,docker安装Awesome TTRSS”

  1. Changed the docker-compose.yml file, SELF_URL_PATH = change to a domain name starting with https, and redeploy, accessible via https, but login account times error, Error: Browser check failed: window.requestIdleCallback not Stack trace, kneeling, the environment to say: ttrss deployed in the Docker environment of server B, using server A reverse proxy server B

    1. You first use the ip test function is normal, if normal, in the ordinary http domain name anti-generation, if still normal, then the problem is in the ssl configuration above, focus on checking the ssl configuration this part.

  2. After the reverse proxy with the domain name can not open what is the situation at the beginning with the vps ip no problem can open after changing to the domain name can not open the domain name has resolved to the vps ip

  3. Hello, in accordance with your kind of tutorial, and then is set the domain name out of the question: set https://域名, Pagoda use to install a good certificate and forced to enable, but enter the page prompted the domain name should be set to become http://域名; set the domain name to http://域名 after you can use https://域名 to open on behalf of, after logging in stuck in 30% page pop-up window Prompt should be set to https://域名, and finally can not enter the system. Please teach the gods how to solve this

    1. In your case, don't force ssl to be enabled in the Pagoda backend first, but install a good certificate. Then set up access via https on the RSS side, and test normal access before opening the forced jump.

      1. Yes. I installed it according to the process, but when I enter the domain name, I can display the ttrss login screen, but the login shows 404 not found nginx, please advise please advise

        1. 404 error is generally a problem with pseudo-static settings, you see if you can study it, the best solution is to reinstall the system and start over.

Leave a Comment

Your email address will not be published.

Scroll to Top