azmo/ttrss repository overview

⁠docker-ttrss

⁠Postgres user/permissions

The supplied docker-compose.yml file supports running a postgres container with an arbitrary UID (default is alpine's default of 70). If you do so please see the section on arbitrary --user Notes⁠ for postgres' offical docker image.

⁠Importing existing data

This assumes you are using the supplied docker-compose.yml file.

If your import is overwriting the default database (usually ttrss), which is opened on postgres startup, you need to add an extra \connect postgres statement into your .sql file.

\connect postgres
[...]
DROP database ttrss

If you don't, postgres cannot drop and recreate the open database it is currently using and your import will fail.

Steps for importing data:

• Stop all services: docker-compose down
• Mount your import file into the postgres container:

  volumes:
      [...]
      - <path-to-your-import-file>:/tmp/import
  

  Copy
• Bring the postgres container up: docker-compose up -d postgres
• Get a shell inside the container: docker-compose run postgres /bin/sh
• Execute the import: psql -h postgres -U ttrss -f <path-to-your-import-file>
• Bring the postgres container down for good measure: docker-compose down

You should then be able to bring everything back up with a standard docker-compose up -d. ttrss might prompt you for a schema upgrade if you are importing from an older version after login.