Open aminvakil opened 2 years ago
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog
or Status: In Progress
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
@aminvakil This issue has an update?
@madson7 Nope, but AFAICS docker-compose has fixed lots of its problems since then.
I will continue with a self-hosted fork to accompany the main project, I created a feature branch to customize the installation and update via swarm.
Sorry, I'm new and I don't know the best way to contribute to the project here, if you have any tips or criticisms, feel free.
I will continue with a self-hosted fork to accompany the main project, I created a feature branch to customize the installation and update via swarm.
Sorry, I'm new and I don't know the best way to contribute to the project here, if you have any tips or criticisms, feel free.
Sorry for late response, I'm not sure if there is interest in changing current state with docker-compose by maintainers.
Problem Statement
docker-compose
is getting worse with each release and can't be relied on even for testing products as it will break more and more.Solution Brainstorm
Maybe we can change the current situation to use a single node swarm cluster.