Skip to content

New Content: docker-compose clarification #500

@maxibenner

Description

@maxibenner

Is there a topic or section missing from the docs? Please describe.
The section on docker-compose could use a few more details. I'd be happy to make a PR if everyone agrees that this would be useful.

Describe the content you'd like to see added:
I'd add a section (maybe a callout) that notes the following:

  1. Which configuration doesn't need to be added because coolify adds it automatically e.g. volumes, container_name, restart.
  2. That images should be pinned to a particular version (as opposed to latest) to prevent the template from breaking due to upstream changes.

Why is this content important?
I've noticed that there are certain recurring change requests for the docker-compose files when people create PRs for new services. I think mentioning those could save maintainers time by not having to repeatedly making those change requests.

Additional context
See this PR and my own PR as examples of these common issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions