@ -10,7 +10,6 @@ General outline of the configuration is as follows:
- separate containers (frontend: nginx, 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
- database schema is installed automatically if it is missing
- database schema is installed automatically if it is missing
- nginx 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 (deprecated)
- optional SSL support via Caddy w/ automatic letsencrypt certificates (deprecated)
@ -39,7 +38,8 @@ remove ``127.0.0.1:`` from ``HTTP_PORT`` variable in ``.env``.
Please don't rename the services inside `docker-compose.yml` unless you know what you're doing. Web container expects application container to be named `app`, if you rename it and it's not accessible via Docker DNS as `http://app` you will run into 502 errors on startup.
Please don't rename the services inside `docker-compose.yml` unless you know what you're doing. Web container expects application container to be named `app`, if you rename it and it's not accessible via Docker DNS as `http://app` you will run into 502 errors on startup.
You can customize other `config.php` defines using environment variables (see `app/Dockerfile` for complete list).
Main configuration file (`config.php`) is rewritten on startup, don't edit it manually. Use environment variables
(see `app/Dockerfile` for complete list) or use `config.d` snippets to customize it.
Andrew Dolgov
4 years ago