AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Edit history

Earlier versions of Selfhosted: Missing dependencies in docker-compose.yaml, newest first.

Current version | Edited by Rex
Changes
As somebody who was manually translating docker-compose.yaml into a quadlet for podman, these little things threw me off. *Maybe* they can cause small issues if services launch in wrong order on docker. Not a biggie but thought of referencing it here.Removed: ### LocationRemoved: Removed: _No response_Removed: ### Suggested changeAdding `postgres: {condition: service_healthy}` to these two.Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched existing issues.Removed: - ☑ I wrote this report in my own words, except for direct translation if needed.
Show

Selfhosted: Missing dependencies in docker-compose.yaml

What needs fixing?

users-shard depends on postgres and nats but only has nats as dependency https://github.com/fluxerapp/fluxer/blob/main/deploy/self-hosting/docker-compose.yml#L312 app-proxy depends on postgres but only has API and Caddy as dependency https://github.com/fluxerapp/fluxer/blob/main/deploy/self-hosting/docker-compose.yml#L280 As somebody who was manually translating docker-compose.yaml into a quadlet for podman, these little things threw me off. Maybe they can cause small issues if services launch in wrong order on docker. Not a biggie but thought of referencing it here.

Suggested change

Adding postgres: {condition: service_healthy} to these two.
Original by Rex
Show

Selfhosted: Missing dependencies in docker-compose.yaml

What needs fixing?

users-shard depends on postgres and nats but only has nats as dependency https://github.com/fluxerapp/fluxer/blob/main/deploy/self-hosting/docker-compose.yml#L312 app-proxy depends on postgres but only has API and Caddy as dependency https://github.com/fluxerapp/fluxer/blob/main/deploy/self-hosting/docker-compose.yml#L280 As somebody who was manually translating docker-compose.yaml into a quadlet for podman, these little things threw me off. Maybe they can cause small issues if services launch in wrong order on docker. Not a biggie but thought of referencing it here.

Location

No response

Suggested change

Adding postgres: {condition: service_healthy} to these two.

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.