Skip to content

changes to compose file not propagated on restart #3

Description

@bdentino

original yml contents are cached and used to restart the service. Need to intelligently relaunch services when their compose files change (remove deleted services, watch/unwatch changed volumes, load new externals, etc). Until the code is a little more organized though, this is gonna be more complicated than it's worth i think.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions