[RFC] Plugin system about docker-starter HOT 3 CLOSED

Hello,

Thanks for raising this up. But we already discuss that (internally). To summary, we prefer to keep something simple, with the minimum code to avoid shipping to much code in a simple application. And also to avoid end user to remove lot of code. Instead we prefer to add many cookbooks in the main README (which will be deleted in end user app).

I think I still have the same opinion on this topic.

ATM, you can have multi-application with worker, cron, redis, rabbitmq, es, postgres, mercure, etc very quickly (<10 minutes) by copying the main the README. It's almost a no-brainer task so it should be easy for everyone.

But I'm not close for new features, but on this one I prefer the documentation over a plugin system.

Let's wait to know what other people think about it before taking an decision

from docker-starter.

I agree with @lyrixx. Too much work to maintain a plugin system IMO. 👎 from me

from docker-starter.

I'm not in favor of a plugin system. Cookbooks are a very nice option. All of common docker/php project have a same base (frontend, database). All others services depends of the project itself. As @lyrixx says, it's quite simple and fast to add Elasticsearch, Mercure, even switch from pgsql to mariadb. I think that adding a plugin system will make harder and more complex the maintenance of this project. So, 👎 for me too

from docker-starter.