Contrib-pointers for additional Services and techniques

[mkrauser]

I recently tested the proposed integration of Elastic Search (#1320), which was not adopted due to the lack of a wider community interest.

But for some developers, like myself, this would be very handy.

I understand, that ddev cannot support every service out there. But what about creating a contrib-repository, where additional services can be contributed and managed by the community.

That way, there would be a central place, to look for additional services.

I got this idea from Symfony Flex. The core-recipies (https://github.com/symfony/recipes) for flex are maintained by the Symfony project, but theres also a contrib-repository (https://github.com/symfony/recipes-contrib) which is manage by the community.

[rfay]

Thanks for this good idea. We'll take a look at those other examples. I'm not sure how a free-form contrib repo could be organized though.

[rfay]

I find myself regularly pointing people to a small set of articles and Stack Overflow articles. I'm thinking that we just need a good (and maintained) list of pointers. Not sure whether it should be a repo or something else. Maybe it should be a docs page.

[mkrauser]

Of course, that would also help a lot! But let me point out some advantages, if people can provide their recipies for services directly in a git-repo:

Not everyone who implements custom services for ddev publishes them on SO or anywhere else. With a Contrib-Repo, we would have that single place anyone could contribute their hacks. And it may encourage people to publish.
Also if one solution is outdated or has issues, the community could work on that. This would be complicated with links to SO or any other websites.

Like I said, a maintained list of links would also help, but I would love to see a repo.

[rfay]

Added awesome-ddev for external resources.

Created ddev-contrib for exactly this use-case.

[rfay]

ddev-contrib and awesome-ddev are open for business. @mkrauser how about a PR (sorry for the do-over) for elasticsearch there?