Mercurial > libervia-backend
view docker/web-demo.yml @ 4002:5245b675f7ad
plugin XEP-0313: don't wait for MAM to be retrieved in connection workflow:
MAM retrieval can be long, and can be done after connection, message just need to be
sorted when being inserted (i.e. frontends must do insort).
To avoid blocking connection for too long and result in bad UX and timeout risk, one2one
MAM message are not retrieved in background.
author | Goffi <goffi@goffi.org> |
---|---|
date | Fri, 10 Mar 2023 17:22:45 +0100 |
parents | 87caf6284c55 |
children |
line wrap: on
line source
version: "3.6" services: prosody: image: libervia/prosody:demo depends_on: # we need to depend on backend to get IP address of the container for conf - backend tmpfs: - /var/log/prosody networks: default: aliases: - server1.test db: image: postgres environment: POSTGRES_PASSWORD: test_e2e POSTGRES_DB: pubsub tmpfs: /var/lib/postgresql/data pubsub: image: libervia/pubsub depends_on: - db - prosody environment: PGHOST: db PGUSER: postgres PGPASSWORD: test_e2e LIBERVIA_PUBSUB_RHOST: server1.test LIBERVIA_PUBSUB_JID: pubsub.server1.test LIBERVIA_PUBSUB_XMPP_PWD: test_e2e backend: image: libervia/backend:dev-demo volumes: - libervia-web-demo_data:/home/libervia/.local/share/libervia ports: # HTTP Upload - "7777:7777" networks: default: aliases: - libervia-backend.test web: image: libervia/web:dev-demo depends_on: - backend environment: LIBERVIA_PASSPHRASE: test_demo volumes: - libervia-web-demo_data:/home/libervia/.local/share/libervia ports: - "8880:8880" networks: default: aliases: - libervia-web.test volumes: libervia-web-demo_data: