|
|
|
@ -7,12 +7,12 @@ The idea is to provide tt-rss working (and updating) out of the box with minimal
|
|
|
|
|
|
|
|
|
|
|
|
General outline of the configuration is as follows:
|
|
|
|
General outline of the configuration is as follows:
|
|
|
|
|
|
|
|
|
|
|
|
- separate containers (frontend: caddy, database: pgsql, app and updater: php/fpm)
|
|
|
|
- separate containers (frontend: nginx, database: pgsql, app and updater: php/fpm)
|
|
|
|
- tt-rss updates from git master repository on container restart
|
|
|
|
- tt-rss updates from git master repository on container restart
|
|
|
|
- tt-rss source code is stored on a persistent volume so plugins, etc. could be easily added
|
|
|
|
- tt-rss source code is stored on a persistent volume so plugins, etc. could be easily added
|
|
|
|
- ``config.php`` is generated if it is missing
|
|
|
|
- ``config.php`` is generated if it is missing
|
|
|
|
- database schema is installed automatically if it is missing
|
|
|
|
- database schema is installed automatically if it is missing
|
|
|
|
- Caddy has its http port exposed to the outside
|
|
|
|
- nginx has its http port exposed to the outside
|
|
|
|
- optional SSL support via Caddy w/ automatic letsencrypt certificates
|
|
|
|
- optional SSL support via Caddy w/ automatic letsencrypt certificates
|
|
|
|
- feed updates are handled via update daemon started in a separate container (updater)
|
|
|
|
- feed updates are handled via update daemon started in a separate container (updater)
|
|
|
|
- optional backups container which performs tt-rss database backup once a week
|
|
|
|
- optional backups container which performs tt-rss database backup once a week
|
|
|
|
|
fox
4 years ago