This proposed change includes tweaks to the names of the services and volumes, and adds an explicit label to the postgres and freshrss containers.
Using a more generic "freshrss-db" instead of "freshrss_postgresql" seems more standard among other docker projects and makes it a bit easier to switch databases later.
Removing the "freshrss_" prefix from the volume names solves a problem where the docker-compose automatically prepends a "project name" to volume names upon running "up". So if your docker-compose.yml file is stored in a folder named "freshrss", you would end up with a redundant volume name of "freshrss_freshrss_data".
This also adds a restart policy to the db container.
* New core-extensions to allow Docker volumes for third-party extensions
#Fix https://github.com/FreshRSS/FreshRSS/issues/2650
Split our extensions directory into two:
1) Core extensions shipped with FreshRSS in ./lib/core-extensions/
2) Third-party extensions modified by end-users in ./extensions/ which
can easily be mounted as a Docker volume
* Example of Docker Compose with extensions
* Back-compatibility + fix array merge bug
* Add a docker compose example.
Using postgresql and with traefik specific labels.
* Added docker-compose specific documentation.
* Move docker-compose section at the end of the README.md.
* Correct docker-compose.yml file and add a corresponding note in the doc.
* Typo in doc.
* Add a docker compose example.
Using postgresql and with traefik specific labels.
* Added docker-compose specific documentation.
* Move docker-compose section at the end of the README.md.
Germs2004
Mike Vanbuskirk
Alexandre Alapetite
Upils