@ -54,7 +54,9 @@ Having trouble getting the above to run?
This is the detailed installation walkthrough.
This is the detailed installation walkthrough.
If you've already followed the [quickstart ](#quickstart ) guide and everything works, you can skip this part.
If you've already followed the [quickstart ](#quickstart ) guide and everything works, you can skip this part.
### Running
### Select database
This container requires a PostgreSQL or MySQL database instance.
Following docker's best practices, this container does not contain its own database,
Following docker's best practices, this container does not contain its own database,
but instead expects you to supply a running instance.
but instead expects you to supply a running instance.
@ -63,28 +65,61 @@ database instance and configuration you're relying on.
Also, this makes this container quite disposable, as it doesn't store any sensitive
Also, this makes this container quite disposable, as it doesn't store any sensitive
information at all.
information at all.
#### Starting a database instance
#### PostgreSQL container
This container requires a PostgreSQL database instance. You're free to pick (or build)
The recommended way to run this container is by linking it to a PostgreSQL database instance.
any, as long as is exposes its database port (5432) to the outside.
You're free to pick (or build) any PostgreSQL container, as long as it exposes
its database port (5432) to the outside.
Example:
Example with nornagon/postgres :
```bash
```bash
$ sudo docker run -d --name=ttrssdb nornagon/postgres
$ docker run -d --name=tinydatabase nornagon/postgres:latest
```
```
#### Testing ttrss in foreground
> The image nornagon/postgres exposes a database superuser that this image uses
to automatically create its user and database,
so you don't have to setup your database credentials here.
For testing purposes it's recommended to initially start this container in foreground.
Use the following database options when running the container:
This is particular useful for your initial database setup, as errors get reported to
the console and further execution will halt.
```
--link tinydatabase:db
```
#### MySQL container
If you'd like to use ttrss with a mysql database backend, simply link it to a
mysql container instead.
You're free to pick (or build) any MySQL container, as long as it exposes
its database port (3306) to the outside.
Example with sameersbn/mysql:
```bash
```bash
$ sudo docker run -it --link ttrssdb:db -p 80:80 clue/ttrss
$ docker run -d --name=tinydatabase -e DB_USER=ttrss -e DB_PASS=ttrss -e DB_NAME=ttrss sameersbn/mysql:latest
```
> The image sameersbn/mysql does not expose a database superuser,
so you have to explicitly pass the database credentials here.
Use the following database options when running the container:
```
--link tinydatabase:db
```
#### External database server
If you already have a PostgreSQL or MySQL server around off docker you also can go with that.
Instead of linking docker containers you need to provide database hostname and port like so:
```
-e DB_HOST=172.17.42.1
-e DB_PORT=3306
```
```
##### Database configuration
### Database configuration
Whenever your run ttrss, it will check your database setup. It assumes the following
Whenever your run ttrss, it will check your database setup. It assumes the following
default configuration, which can be changed by passing the following additional arguments:
default configuration, which can be changed by passing the following additional arguments:
@ -95,7 +130,15 @@ default configuration, which can be changed by passing the following additional
-e DB_PASS=ttrss
-e DB_PASS=ttrss
```
```
##### Database superuser
If your database is exposed on a non-standard port you also need to provide DB_TYPE set
to either "pgsql" or "mysql".
```
-e DB_TYPE=pgsql
-e DB_TYPE=mysql
```
### Database superuser
When you run ttrss, it will check your database setup. If it can not connect using the above
When you run ttrss, it will check your database setup. If it can not connect using the above
configuration, it will automatically try to create a new database and user.
configuration, it will automatically try to create a new database and user.
@ -109,7 +152,17 @@ following additional arguments:
-e DB_ENV_PASS=docker
-e DB_ENV_PASS=docker
```
```
#### Running ttrss daemonized
### Testing ttrss in foreground
For testing purposes it's recommended to initially start this container in foreground.
This is particular useful for your initial database setup, as errors get reported to
the console and further execution will halt.
```bash
$ docker run -it --link tinydatabase:db -p 80:80 clue/ttrss
```
### Running ttrss daemonized
Once you've confirmed everything works in the foreground, you can start your container
Once you've confirmed everything works in the foreground, you can start your container
in the background by replacing the `-it` argument with `-d` (daemonize).
in the background by replacing the `-it` argument with `-d` (daemonize).
@ -117,5 +170,5 @@ Remaining arguments can be passed just like before, the following is the recomme
minimum:
minimum:
```bash
```bash
$ sudo docker run -d --link tinystor e:db -p 80:80 clue/ttrss
$ docker run -d --link tinydataba se:db -p 80:80 clue/ttrss
```
```