# Nodejs, elasticsearch, jekyll( or any other static html generator) on (GitHub pages)

**URL:** <https://discuss.elastic.co/t/nodejs-elasticsearch-jekyll-or-any-other-static-html-generator-on-github-pages/5468>\
**Category:** Elasticsearch\
**Created:** [September 28, 2011, 8:54am UTC](https://discuss.elastic.co/t/nodejs-elasticsearch-jekyll-or-any-other-static-html-generator-on-github-pages/5468 "2011-09-28T08:54:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yevgeni](https://avatars.discourse-cdn.com/v4/letter/y/3bc359/32.png) [@yevgeni](https://discuss.elastic.co/u/yevgeni)\
**Post date:** [September 28, 2011, 8:54am UTC](https://discuss.elastic.co/t/nodejs-elasticsearch-jekyll-or-any-other-static-html-generator-on-github-pages/5468/1 "2011-09-28T08:54:39Z")

</div>

Hello,  
Excuse my noobness, but just discovered elasticsearch and some other  
projects and was wondering on how best to implement this.

I would like to build a site that is statically generated using  
Jekyll, this has a Search button, like in the example here  
[http://blog.jodet.com/jekyll-and-node/](http://blog.jodet.com/jekyll-and-node/)

Although in my case I will have many gh-pages sites running their own  
minisites based on the 'master' code of the first instance.

For example, I would like each member of my community to be able to  
clone the code for the static website, put it on their own GitHub  
page, add some blog entries and for these blog entries to be indexed  
by Elastic Search, and then when a user makes a search the results  
returned will be for this site, and all the other member sites.

All the member sites will have their own domain name URI, so i will  
need to think about cross-domain issues, when indexing the data and  
when making the actual searches.

At the start, I will just use a single server to run nodejs,  
elasticsearch in order to index the data.

Does this make sense or can it be done simpler, if so how? Can someone  
port the [http://blog.jodet.com/jekyll-and-node/](http://blog.jodet.com/jekyll-and-node/) to use ElasticSearch  
instead of SQLLite.

I see there is already a port [https://github.com/ncb000gt/node-elasticsearch](https://github.com/ncb000gt/node-elasticsearch)  
available and I will try to get this working, but would like to know  
if this approach is viable and most importantly scalable?

Thanks

yevgeni

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:53am UTC](https://discuss.elastic.co/t/nodejs-elasticsearch-jekyll-or-any-other-static-html-generator-on-github-pages/5468/2 "2017-07-06T03:53:25Z")

</div>

Closed on July 6, 2017, 3:53am UTC


