> if you find yourself using amazing open source products like Typesense which you want to continue to see flourish, we encourage finding out how you or your organization can support them, either via direct contributions or by helping spread the word with public posts (like this) sharing your experiences as their continued success will encourage further investments that ultimately benefits the project and all its users.
Couldn't agree more! An easy way to support an open source project is to talk and/or write about how you use the project in your stack. This is a big help to the project's continued success - it helps build credibility especially with new users, and it is also a big motivation for the authors to see their work being adopted and used in different contexts.
As one of the authors of Typesense I was really stoked to see this article pop up on Twitter this morning, and now on HN! Thank you OP for writing such a detailed article and also the comment above.
No worries! It was such an easy win for our docs site, I really think this should be the default approach using your Typesense provided hosting or custom as we did and still sponsoring your work.
Most technical documentation sites I think will be relatively small like our (<100MB), the approach of hosting a dockerized image of typesense might be something others would prefer to keep the management of the service as simple as they can. Would be a handy service and a way to get more people to realize how good Typesense is when applied like this.
2 comments
[ 2.9 ms ] story [ 17.7 ms ] threadCouldn't agree more! An easy way to support an open source project is to talk and/or write about how you use the project in your stack. This is a big help to the project's continued success - it helps build credibility especially with new users, and it is also a big motivation for the authors to see their work being adopted and used in different contexts.
As one of the authors of Typesense I was really stoked to see this article pop up on Twitter this morning, and now on HN! Thank you OP for writing such a detailed article and also the comment above.
Most technical documentation sites I think will be relatively small like our (<100MB), the approach of hosting a dockerized image of typesense might be something others would prefer to keep the management of the service as simple as they can. Would be a handy service and a way to get more people to realize how good Typesense is when applied like this.