Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

usage of gravo in docker compose #13

Open
muc-patrick opened this issue Nov 10, 2020 · 1 comment
Open

usage of gravo in docker compose #13

muc-patrick opened this issue Nov 10, 2020 · 1 comment

Comments

@muc-patrick
Copy link

Hi *,

short question from my side.
How can I address the api to the middleware by using docker compose?
I haven't find any way, see below my docker-compose.yml:

`Service:
...

volkszaehler:
image: volkszaehler/volkszaehler
ports:
- 8079:8080
# NOTE: The init command will only work once the database is fully up and running.
# By putting restart: always docker-compose will retry starting this container
# and finally complete the database setup sequence.
command: sh -c "
sed -i s/localhost/database/ /vz/etc/config.yaml &&
sed -i s/vz_admin/root/ /vz/etc/config.yaml &&
sleep 1 &&
(/vz/bin/doctrine orm:schema-tool:update --force || /vz/bin/doctrine orm:schema-tool:create) &&
/vz/vendor/bin/ppm start -c /vz/etc/middleware.json --static-directory /vz/htdocs --cgi-path=/usr/local/bin/php"
links:
- database
depends_on:
- database
networks:
- volkszaehler
restart: always

gravo:
image: andig/gravo
ports:
- 8000:8000
command:
- -api http://ip:8080
links:
- volkszaehler
networks:
- volkszaehler
restart: always

...
`

@psych0d0g
Copy link

  gravo:
    image: andig/gravo
    ports:
    - 8000:8000
    entrypoint: [/usr/bin/gravo, -api, http://volkszaehler:8080]
    links:
    - volkszaehler
    depends_on:
    - volkszaehler
    networks:
    - volkszaehler
    restart: always

that way it works for me

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants