WIP: Docker GCIS #555
WIP: Docker GCIS #555
Conversation
|
Added Next step. run |
Tuba.conf is now set only as a volume in the docker compose. Tuba.conf is now sourced from a docker specific sample conf. gcis image is not tagged as latest instead of small. postgres compose now sources db init from db/docker Tuba.pm logs its version on startup
|
Everything seems to be working! Going to install from scratch on another machine to test. |
| 1. the `content_2` file should be moved to `./db/docker/4_content_2.sql` | ||
| - if you want an empty GCIS instance, only copy the schema & content 1. | ||
| 1. run `docker-compose up postgres` | ||
| - Refresh your tea. |
| 1. Setup postgres *alone* first | ||
| 1. Download the latest [public content release](https://github.com/USGCRP/gcis/releases) | ||
| 1. Untar the files | ||
| 1. the `schema` file should be moved to `./db/docker/2_schema.sql` |
There was a problem hiding this comment.
In a future release, consider handling this in the gcis container's entrypoint.sh. Basically, have it check for an empty database when it comes up and then psql schema content_1 content_2 from a bind mount into the database.
There was a problem hiding this comment.
Filed #557, to avoid forgetting.
| @@ -0,0 +1,19 @@ | |||
| -----BEGIN CERTIFICATE----- | |||
There was a problem hiding this comment.
Correct. Just exists to test the https protocol. Throws a lovely "this is self signed!1!!1" in both Chrome and Firefox but gets the job done.
Continuation of PR #478