@@ -34,19 +34,19 @@ Place [`.env`](#env) and [`docker-compose.yml`](#docker-composeyml) (contents be
3434
35351 . Create a directory for your tt-rss installation. Do the remaining steps in there.
36362 . Create a ` .env ` file using [ ` .env ` ] ( #env ) as a starting point; edit it to suit your needs (e.g. adjusting ` HTTP_PORT ` ).
37- * Consider changing password/secret environment variables to something you're comfortable with (e.g. ` pwgen ` -generated values).
38- 4 . Create a ` docker-compose.yml ` file using [ ` docker-compose.yml ` ] ( #docker-composeyml ) as a starting point; edit it to suit your needs
37+ * Consider changing password/secret environment variables to something you're comfortable with (e.g. ` pwgen ` -generated values).
38+ 3 . Create a ` docker-compose.yml ` file using [ ` docker-compose.yml ` ] ( #docker-composeyml ) as a starting point; edit it to suit your needs
3939 (e.g. enabling the ` backups ` container, using the ` ghcr.io ` images, using a newer ` postgres ` image, etc.).
40- 5 . Run [ ` docker compose up -d ` ] ( https://docs.docker.com/reference/cli/docker/compose/up/ ) to bring up the environment.
41- * Note that the ` -d ` will result in the containers running in the background, which is generally what you want.
42- 6 . Review containers logs and states. Some typical ways this may be done include:
43- * Running commands like [ ` docker compose ps ` ] ( https://docs.docker.com/reference/cli/docker/compose/ps/ ) and [ ` docker compose logs ` ] ( https://docs.docker.com/reference/cli/docker/compose/logs/ )
44- * Using a third-party tool like [ ` lazydocker ` ] ( https://github.com/jesseduffield/lazydocker ) (a terminal UI for Docker and Docker Compose).
45- 7 . Access tt-rss in your browser.
46- * The URL to use depends upon how you set things up, but assuming you kept ` HTTP_PORT=127.0.0.1:8280 ` in your ` .env ` file and are on the same system
47- as tt-rss, you'd use < http://127.0.0.1:8280/tt-rss > .
48- 8 . Log in as ` admin ` or (if you enabled the related environment variables) the auto-created user.
49- * See comments in [ ` .env ` ] ( #env ) regarding the password(s).
40+ 4 . Run [ ` docker compose up -d ` ] ( https://docs.docker.com/reference/cli/docker/compose/up/ ) to bring up the environment.
41+ * Note that the ` -d ` will result in the containers running in the background, which is generally what you want.
42+ 5 . Review containers logs and states. Some typical ways this may be done include:
43+ * Running commands like [ ` docker compose ps ` ] ( https://docs.docker.com/reference/cli/docker/compose/ps/ ) and [ ` docker compose logs ` ] ( https://docs.docker.com/reference/cli/docker/compose/logs/ )
44+ * Using a third-party tool like [ ` lazydocker ` ] ( https://github.com/jesseduffield/lazydocker ) (a terminal UI for Docker and Docker Compose).
45+ 6 . Access tt-rss in your browser.
46+ * The URL to use depends upon how you set things up, but assuming you kept ` HTTP_PORT=127.0.0.1:8280 ` in your ` .env ` file and are on the same system
47+ as tt-rss, you'd use < http://127.0.0.1:8280/tt-rss > .
48+ 7 . Log in as ` admin ` or (if you enabled the related environment variables) the auto-created user.
49+ * See comments in [ ` .env ` ] ( #env ) regarding the password(s).
5050
5151### .env
5252
0 commit comments