Updated Docker image (markdown)

Jyri-Petteri Paloposki 2020-07-17 13:00:05 +03:00
parent d1c2a3d56f
commit 59b50c0d1e

@ -1,5 +1,7 @@
Docker is the easiest way to run Tracks, as the various library requirements have already been taken care of for you.
## Official Docker image
You can run Tracks by installing Docker and launching a MySQL instance for example using
$ docker run --name mariadb -t mariadb
@ -12,4 +14,30 @@ And then run an instance of the image using the following command (but replacing
$ docker run -p 3000:3000 -e DATABASE_NAME=tracks_dev -e DATABASE_HOST=db -e DATABASE_PORT=5432 -e DATABASE_USERNAME=tracks_dev -e DATABASE_PASSWORD=password -e DATABASE_TYPE=mysql2 --name tracks --link mariadb:db -t tracks
If all went to plan, you should now be able to reach Tracks in http://localhost:3000 .
If all went to plan, you should now be able to reach Tracks in http://localhost:3000 .
## Staannoe's Dockerimage
### Prerequisites
Docker installed on the host machine
Tracks is a web-based application to help you implement David Allens Getting Things Done™ methodology. It was built using Ruby on Rails.
This is the easy way getting up and running with Tracks, which is one of the greatest software implementations of the GTD™ methodology.
This builds main parts are:
* Tracks 2.3.0 (stable)
* Ubuntu 14.04
* Tracks 2.2.3
* Apache 2 (Passenger)
* Sqlite3
* Dockerize (Utility to simplify running applications in docker containers)
It utilizes mostly native Ubuntu 14.04 packages, thus rebuilding it will provide the latest updates.
For production use it is highly recommended to update the `site.yml.template` within the build repo, rename it to `site.yml` then rebuild the container.
Example on how to run the Tracks container:
docker run -d --name=tracks -p 80:80 staannoe/tracks