[Developer Experience] Automate Local Environment Setup about blockbuilder-search HOT 5 OPEN

yea, this is a great idea. containerizing things would make deployment easier too.

from blockbuilder-search.

I'd appreciate this as well.

from blockbuilder-search.

@micahstubbs I've started to look into this just to see how local setup works, and there are quite a few independent pieces that could go into this. The more I look at it, the more unsure I am about whether it makes sense to make a Dockerfile just for blockbuilder-search, or if it should go over into the home blockbuilder repository.

How would we feel about having some fixture gists so someone can start developing without having to scrape real data? If we like that idea, which repository feels like the natural home to put the fixture data?

from blockbuilder-search.

@hydrosquall I think a Dockerfile for blockbuilder + blockbuiler-search together in the https://github.com/enjalot/blockbuilder repo is the right path.

a separate Dockerfile for the search index in Elasticsearch that we build with the scripts in blockbuilder-search-index would also be a nice area for future work

from blockbuilder-search.

@hydrosquall I think that this is the best place for fixture data / sample data https://github.com/enjalot/blockbuilder-search-index/tree/master/data

that said, not sure if putting the fixture data in a different repo from the Dockerfile is too much indirection (looks organized to me, might look confusing to a new contributor...)

from blockbuilder-search.